Next has become the first major British high street retailer to sell more to its customers online than through its network of more than 500 stores.
The historic crossover came at the start of the new financial year in February, according to chief executive Lord Wolfson, with the gap set to widen rapidly through 2019.
It will send further shockwaves through a battered retail sector already struggling to adapt to the accelerating shift from “bricks and mortar” to digital sales.
Wolfson hails this as a thing worth embracing, saying that people in small provincial towns now have the same buying options as those who shopped on Oxford Street ten years ago. Everybody wins, right? Not exactly.
If you’re a person with a disability, Next has gone to the trouble of building a separate website which supposedly cators to the needs of those who need accessibility. Problem is, separate is not equal, and it never has been.
This is another one of those conversations we shouldn’t be having at this point in the web’s history. For one thing, as already mentioned, separate is not equal, and even law/policy, as incoherent as it is, agrees on this, at least when it comes to certain industries.
For another thing, separate websites for people with disabilities are often not maintained, (looking at you, Amazon), and are a resource vampire for both the establishment for which they’re built as well as any web design or development staff, in or out of house. If anyone seriously suggested thata we build separate websites for phones, tablets, large screens and watches, they’d be laughed out of the room by pretty much anyone who builds or designs things for the web. No one would dream of wastiing time and resources like that. So why is it still all too common to see large organizations building separate websites for people with disabilities?
Web-based discrimination is just as unacceptable as real-world discrimination. It’s not OK to build separate but equal for browsers, and it’s not OK to build separate but equal for people either, and people with disabilities are people first and foremost. Seriously, if you’re a web developer or designer and you’re being asked to build a separate site for accessibility purposes, please push back on this. I’m not going to lie, you may have to walk awa from a contract or to. We, however, are the only ones who can really change this situation. These things wouldn’t be built unless we as an industry weren’t willing to put in the elbow grease to build them. We’re not just pairs of hands, and if we as an industry could manage to move the needle from building one-size-fits-all websites to building websites responsively, then we can move the separate but equal needle too. Let’s do this already.
The federal government is accusing Facebook of illegally using its advertising platform to discriminate against people with disabilities and other groups.
The U.S. Department of Housing and Urban Development charged the social media company Thursday with violating the Fair Housing Act. The agency said Facebook is “encouraging, enabling and causing housing discrimination” through its method of allowing advertisers to control who sees ads for homes. … According to the charge, Facebook allows advertisers to exclude or include users from seeing ads based on various attributes including interests in “accessibility” or “service animal.”
Furthermore, the charge alleges that Facebook’s system is set up in such a way that it won’t show ads to groups it considers unlikely to engage with them, even if the advertiser has explicitly targeted those groups.
As a result, “ads for housing and housing-related services are shown to large audiences that are severely biased based on characteristics protected by the (Fair Housing) Act,” according to the charge.
At last year’s National Federation of the Blind convention, Facebook stated that
one in ten people use the zoom feature on the desktop browser, 20 percent of people increase the font size on iOS, and over 100,000 use screen readers on mobile devices to view Facebook.
(Source). It didn’t take very long for what amounts to tracking those with disabilities to go from something benign to something used as a tool of discrimination. The fact that the self-styled “voice of the nation’s blind” essentially aided and abetted this isn’t surprising. And yes, the NFB owns part of this. That organization gave Facebook a platform and its blessing to essentially brag about its disability tracking efforts, and were silent when questions were raised concerning how that data was gathered. If I were a member I’d be pretty pissed right now and I’d be demanding answers from the leadership.
There is, however, one new feature for VoiceOver users: a new option called ‘Accessibility Events’ located at Settings > General > Accessibility > VoiceOver > Web. This option is enabled by default, with Apple saying that Accessibility Events:
… allow websites to customize their behaviour for assistive technologies, like VoiceOver. Enabling Accessibility Events may reveal whether an assistive technology is active on your iPhone.
We’re currently unaware of any websites which take advantage of this facility, so do please let us know in the comments if you know more about this feature and any websites where it can be seen in action.
This is just as bad of an idea as Google’s “ask-for-alt-text” feature. I will definitely be turning this off when I update my devices because sorry fellow developeres, you cannot haz that data. These settings, including the automatic opt-in, also apply to Mac OS Mojave, (OSX 10.14.4). This version of OSX was released on the same day as iOS 12.2. I’ll also be encouraging everyone else, (in the strongest possible terms), to do the same. Seriously, why is it so difficult to just make websites accessible in the first place? Why do we have to keep having this conversation? We’ve seen what happens when data is managed irresponsibly, (and that’s putting it lightly), and as neither a society nor an industry are we even close to equipped to handle something as sensitive as screen reader tetection with any kind of care. What’s Apple going to do, release some ethical guidelines? Even if they did this, how are they supposed to enforce them? And never mind developers screwing this up by using it as it probably wasn’t intended. It happened with HTML, it’ll happen with screen reader detection too.
If, like me, you are concerned about your privacy with regard to your disability, you’ll need to explicitly opt out, on both iOS and OSX. Consult either your device’s documentation, (VoiceOver for iOS or VoiceOver for the Mac), or a suitable book written for assistive technology users by assistive technology users. The one I wholeheartedly recommend is iOS Access for All: Your Comprehensive Guide to Accessibility for iPad, iPhone, and iPod Touch, by Shelly Brisbin.
Specific link text sets sincere expectations and fulfills them, and is substantial enough to stand alone while remaining succinct.
So, score one more for accessibility benefiting everyone. And, if you’re not doing so already, spend some time putting some thought into your link text. If you’re using social media as your personal or professional home on the web, here’s one more reason to consider either starting your own website, or hiring someone to build one for you.
While php 5.6 reached end-of-life as of December 31, 2018, WordPress’s step to make it the minimum allowed version while continuing to encourage usage of php 7.2 and above is an important one. For one thing, it means that securing installations will be just a bit easier, and for another, the minimum allowed version change, coupled with encouragement to use a truly modern version, as well as allowing plugin authors to specify a supported php version, will make life a lot easier for those of us maintaining code.
Most hosts, especially the larger ones, have already either migrated to php 7.2 or above, or are strongly encouraging their users to do so. Note that if you’re running a virtual private server or similar, you will be required to manage the php upgrade yourself. If you happen to be a user or organization running on a virtual private server, and you are not technically proficient enough to manage the upgrade, you’ll want to make arrangements for someone to upgrade for you. I mention this last point because in the laast few weeks I’ve run into a lot of cases where users or organizations have been talked into hosting on a virtual private server or similar which they are unable to manage and which they have no one to manage for them. I’m not sure if this is an actual trend or whether or not I’m just personally/professionally encountering a lot of these. Anyway, think of the web, and upgrade your php installation if you haven’t already.
The important thing about any accessibility plug-in is having a good understanding about what problems are being solved. When we’re talking about font size changes and narration, these are features that already exist in the browser or in assistive technology – adding this to your website does almost nothing. It may help a small number of people in specific situations, but that’s the limit.
The defamation (and negligence) claims against Twitter are blocked by 47 U.S.C. § 230.
These changes are slated for the 2.5 release, which does not yet have a date set. However, you’ll want to keep an eye on your WordPress updates so that you can take advantage of these upcoming accessibility improvements. I’m looking at you, assistive technology sho[ps.
Mailto link code and markup generator with subject, body, cc and bcc. Quickly and easily generate code for those annoying mailto links.
How to use GnuWin32 ported tools like grep.exe and find.exe for forensic log file analysis in Windows Server. In this article I’ll give some real live examples of using these ported GnuWin tools like grep.exe for logfile analysis on Windows servers. The article provides three example, as an alternative to LogParser, because finding spam scripts fast is often very important.
Saotn.org uses used URL Rewrite Outbound Rules in IIS, to offload content from a different server and/or host name. This should improve website performance. Just recently I noticed Outbound Rules conflicted with gzip compressed content. I started noticing HTTP 500 error messages: Outbound rewrite rules cannot be applied when the content of the HTTP response is encoded ("gzip").. Here is how to fix that error. …