- Link o’ the week! Help the CMA help the web – Stuart Langridge on how you can help with the final push for a better web on mobile. Whether you agree with us or not, please tell the CMA what you think.
- Keyboard-Only Scrolling Areas from the Jello Biafra of #a11y, Adrian Roselli
- Firefox rolls out Total Cookie Protection by default to all users worldwide “making Firefox the most private and secure major browser available across Windows, Mac and Linux.”
- Meet Web Push in Safari! I like that Safari won’t hassle me to subscribe to push notifications without a user gesture, and settings are integrated. Presumably same for iOS and iPad next year. Good to see this work happening.
- The CMA Final Report on the Mobile Ecosystems market study: a repudiation of Apple’s narrative over privacy and safety as justifications for the status quo – “Apple submitted that the WebKit restriction is primarily motivated by security considerations… CMA concluded that the WebKit restriction is unlikely to be justified by security concerns.”
- Chrome user device characteristics report – Data on device memory, network speeds, number of cores, smallest Android display sizes in BR, DE, EG, GB, ID, IN, JP, NG, US, ZA from Chrome usage stats
- The Email Markup Consortium is “a community-led group of industry professionals working to improve the user experience, accessibility, performance, consistency, and reliability of email markup”
- Japanese regulator’s interim report on Competition Assessment of the Mobile Ecosystem has lots of talk about the #appleBrowserBan, @webkit and PWAs (English, PDF)
- Apple now supports SSML – Speech Synthesis Markup Language. With SSML, you can include multiple ways to say text in a single request, instead of splitting it up into multiple AVSpeechUtterances.
- Using SQL to find my best photo of a pelican according to Apple Photos by Simon “l33t h4xx0r” Willison
- Silicon Valley’s Horrible Bosses – Dispatches From the Elon Musk School of Management
- Talking of hideously toxic workplaces, Kraken Announces Global Hiring Push and Commitment to Crypto-First Culture
Archive for the 'accessibility web standards' Category
My professional other half at Babylon Health, Taylar Bouwmeester, and I invite you to join us on a rollercoaster ride through the merry world of keyboard accessibility. It stars Brad Pitt as me and Celine Dion (she’s Canadian, you know) as Taylar.
- Link o’the week: A Management Maturity Model for Performance – “Despite advances in browser tooling, automated evaluation, lab tools, guidance, and runtimes, however, teams struggle to deliver even decent performance with today’s popular frameworks. This is not a technical problem per se — it’s a management issue, and one that teams can conquer with the right frame of mind and support” by Big Al Russell
- The tech tool carousel by Andy Bell
- Internet Explorer retires on June 15, 2022 – For a long time, it was my browser of choice for downloading Firefox.
- React Native Accessibility – GAAD 2022 Update – React Native accessibility is dragging itself into the 21st century
- HTML Sanitizer API – Chromium & Firefox intend to ship a new HTML Sanitizer API, which developers can use to remove content that may execute script from arbitrary, user-supplied HTML content. The goal is to make it easier to build XSS-free web applications.
- W3C Ethical Web Principles – “The web should be a platform that helps people and provides a positive social benefit. As we continue to evolve the web platform, we must therefore consider the consequences of our work. The following document sets out ethical principles that will drive the W3C’s continuing work in this direction”
- What’s new for the web platform – Jake and Una at Google i/o yesterday showing new web platform features. Highlights: native <dialog> element for popup dialogs that has a11y baked in, the ability to give accent colours in CSS to form controls, declarative lazy loading of off-screen/ less important images. This should allow us to remove hacky components from our web pages, so they’ll be faster (as they’re in the browser) and more likely to be secure and accessible. Can we kill crappy framework dialogs and other form components and replace them with native browser-based equivalents?
- The page transition API uses CSS animations for highly customisable wiggly things to make your sites and PWAs feel more natively app-like. It’s really nice (don’t be put off by Jank Architect’s infomercial demeanour)
- Debugging accessibility with Chrome DevTools – another Google i/o vid
- WordPress’ market share is shrinking – “If WordPress wants to maintain its market share or better yet, grow it, it’ll have to get its act together. That means it should focus on the performance of these sites across the spectrums of site speed and SEO. The Full Site Editing project is simply taking far too long. That’s causing the rest of the platform to lag behind current web trends.”
- Responsive layouts for large screen development – “More than 250 million large screen Android devices are currently in use, including tablets, foldables, and Chrome OS.”
- The UK’s Digital Markets Unit: we’re not making any progress, but we promise we will “in due course” – “at least this document confirms that it is still Government policy to do it “in due course” and “when Parliamentary time allows””
- Porting Zelda Classic to the Web – deep dive into the technical challenge to port an ancient game written in C++ to Web Assembly
Normally, I bang on endlessly about Web Accessibility, but occasionally branch out to bore about other things. For Global Accessibility Awareness Day last week, my employers at Babylon Health allowed me to publish a 30 min workshop I gave to our Accessibility Champions Network on how to make accessible business documents. Ok, that might sound dull, but according to I.M.U.S., for every external document an organisation publishes, it generates 739 for internal circulation. I’m using Google Docs in the talk, but the concepts are equally applicable to Microsoft Word, Apple Pages, and to authoring web content.
It’s introduced by my Professional Better Half, Taylar Bouwmeester –recipient of the coveted “Friendliest Canadian award” and winner of a gold medal for her record of 9 days of unbroken eye contact in the all-Canada Games– and then rapidly goes downhill thereafter. But you might enjoy watching me sneeze, sniff, and cough because I was under constant assault from spring foliage jizzing its pollen up my nostrils. Hence, it’s “R”-rated. Captions are available (obvz) – thanks Subly!
Here is my personal submission to the U.S. National Telecommunications and Information Administration’s report on Competition in the Mobile App Ecosystem. Feel free to steal from it and send yours before before 11:59 p.m. Eastern Time on Monday May 23, 2022. I also contributed to the Open Web Advocacy’s response.
I am a UK-based web developer and accessibility consultant, specialising in ensuring web sites are inclusive for people with disabilities or who experience other barriers to access–such as living in poorer nations where mobile data is comparatively expensive, networks may be slow and unreliable and people are generally accessing the web on cheap, lower-specification devices.
Although I am UK-based, I have clients around the world, including the USA. And, of course, because the biggest mobile platforms are Android and iOS/iPad, I am affected by the regulatory regime that applies to Google and Apple. I write in a personal capacity, and am not speaking on behalf of any clients or employers, past or present. You have my permission to publish or quote from this document, with or without attribution.
Many of my clients would like to make apps that are Progressive Web Applications. These are apps that are websites, built with long-established open technologies that work across all operating systems and devices, and enhanced to be able to work offline and have the look and feel of an application. Examples of ‘look and feel’ might be to render full-screen; to be saved with their own icon onto a device’s home screen; to integrate with the device’s underlying platform (with the user’s permission) in order to capture images from the camera; use the microphone for video conferencing; to send push notifications to the user.
The benefits of PWAs are advantageous to both the developer (and the business they work for) and the end user. Because they are based on web technology, a competent developer need only make one app that will work on iOS, Android, as well as desktop computers and tablets. This write-once approach has obvious benefits over developing a single-platform (“native”) app for iOS in addition to a single-platform app for Android and also a website. It greatly reduces costs because it greatly reduces complexity of development, testing and deploying.
The benefits to the user are that the initial download is much smaller than that for a single-platform app from an app store. When an update to the web app is pushed by a developer to the server, the user only downloads the updated pages, not the whole application. For businesses looking to reach customers in growing markets such as India, Indonesia, Nigeria and Kenya, this is a competitive advantage.
In the case of users with accessibility needs due to a disability, the web is a mature platform on which accessibility is a solved problem.
However, many businesses are not able to offer a Progressive Web App, largely due to Apple’s anti-competitive policy of requiring all browsers on iOS and iPad to use its own engine, called WebKit. Whereas Google Chrome on Mac, Windows and Android uses its own engine (called Blink), and Firefox on non-iOS/iPad platforms uses its own rendering engine (called Gecko), Apple’s policy requires Firefox and Chrome on iOS/iPad to be branded skins over WebKit.
This “Apple browser ban” has the unfortunate effect of ham-stringing Progressive Web Apps. Whereas Apple’s Safari browser allows web apps (such as Wordle) to be saved to the user’s home screen, Firefox and Chrome cannot do so–even though they all use WebKit. While single-platform iOS apps can send push notifications to the user, browsers are not permitted to. Push notifications are high on business’ priority because of how it can drive engagement. WebKit is also notably buggy and, with no competition on the iOS/iPad platform, there is little to incentivise Apple to invest more in its development.
Apple’s original vision for applications on iOS was Web Apps, and today they still claim Web Apps are a viable alternative to the App Store. Apple CEO Tim Cook made a similar claim last year in Congressional testimony when he suggested the web offers a viable alternative distribution channel to the iOS App Store. They have also claimed this during a court case in Australia with Epic.
Yet Apple’s own policies prevent Progressive Web Apps being a viable alternative. It’s time to regulate Apple into allowing other browser engines onto iOS/iPad and giving them full access to the underlying platform–just as they currently are on Apple’s MacOS, Android, Windows and Linux.
Ok, so you’re making a React or React Native app. Don’t! Make a Progressive Web App. Sprinkle some Trusted Web Activity goodness to put it in the Play store wrap it with Capacitor.js if it needs push notifications or to go in the App Store (until the EU Digital Markets Act is ratified so Apple is required to allow more capable browsers on iOS).
But maybe you’re on a project that is already React Native, perhaps because some psycho manager flew in, demanded it and then returned to lurk in Hades. In which case, this might help you.
- Improve Accessibility in Your React App By Managing Focus in Mutable Content – Leverage the component “lifecycle” with useEffect to set the active element in the DOM
- React Native Accessibility – GAAD 2022 Update – official announcement
- Accessibility in React – MDN article to learn about implementing keyboard accessibility in React.
- FocusScope – is a utility component that can be used to manage focus for its descendants, from Adobe’s React ARIA component library
- Creating Accessible React Native Apps – good intro from a Shopify dev
- Accessibility from the official RN docs
- Setting Focus For Accessibility In React Native – the bane of React Native devs’ lives (and of their users’)
I like Expo (and wrote some random Expo tips). Expo Snacks are like ‘codepens’ for React Native.
Open Accessibility bugs – Facebook’s official list, and accompanying blog post.
- Developing a Report on Competition in the Mobile App Ecosystem – The U.S. National Telecommunications and Information Administration is preparing a Report on Competition in the Mobile App Ecosystem, following Biden’s Executive Order to address the problem of “dominant tech platforms undermining competition and reducing innovation”. Includes PWAs and #AppleBrowserBan in scope.
- Questions and Answers: Digital Markets Act: Ensuring fair and open digital markets
- Trust – “many developers are suspicious of browser features but trusting of third-party libraries” by Jeremy keith
- Why I don’t miss React: a story about using the platform by Jack Franklin. Would Facebook ever end React? It was unthinkable that Nokia, Blackberry, MooTools, Internet Explorer would ever disappear. But they did.
- New to the web platform in April – Discover some of the interesting features that landed in stable and beta web browsers during April 2022. By Rachel Andrew
- Celebrating Firefox: How we got to 100 – Aww. I’m pretty sure I started with the preview release. Good times.
- Bundle Buddy – “Visualizing what code is in your web bundle, and how it got there” for all your “we had great DX writing this, why is it so slow and such a network hog and why are our customers using our competitors’ fast apps instead?” needs
- Well Color Us Surprised—This SC Can Be a Tricky Customer – by Ian Lloyd, who doesn’t know how to spell “colour”.
- Global PC shipments pass 340 million in 2021 and 2022 is set to be even stronger – death of desktop exaggerated?
- Changing the face of the web: W3C Web Fonts Working Group and MPEG recognized with a Technology & Engineering Emmy® Award – yes, really; W3C got an Emmy.
- Hack on Bored Ape Yacht Club NFTs leads to $3m simian oblivion – My non-fungible Thoughts and Proof of Prayers to those who have suffered this terrible loss.
USA readers: you have just over 2 weeks to tell the US regulator your thoughts on the Apple Browser Ban, whether you’re in favour of Apple allowing real browser choice on iOS by setting Safari free, or against it. You’re welcome to use Bringing Competition to Walled Gardens, our response to a similar investigation by the UK Competition and Markets Authority for inspiration/ cutting and pasting. Make your voice heard!
In the USA, the National Telecommunications and Information Administration (NTIA) is requesting comments on competition in the mobile application ecosystem after Biden signed Executive Order 14036 on Promoting Competition in the American Economy:
today a small number of dominant internet platforms use their power to exclude market entrants, to extract monopoly profits, and to gather intimate personal information that they can exploit for their own advantage. Too many small businesses across the economy depend on those platforms and a few online marketplaces for their survival
NTIA is looking for “concrete and specific information as to what app developers, organizations, and device (i.e.,phones; tablets) users experience, and any potential challenges or barriers that limit app distribution or user adoption”. Written comments must be received on or before 11:59 p.m. Eastern Time on May 23, 2022.
Several of its questions encompass Apple hamstringing Progressive Web Apps by requiring all iThing browsers use its own bundled WebKit framework, which has less power than Safari or single-platform iOS apps. Here are some of the questions:
- How should web apps (browser-based) or other apps that operate on a mobile middleware layer be categorized?
- What unique factors, including advantages and obstacles, are there generally for app development — especially start-ups — that are relevant for competition?
- Are there studies or specific examples of the costs or advantages for app developers to build apps for either, or both, of the main operating systems, iOS and Android (which have different requirements)?
- What other barriers (e.g.,legal, technical, market, pricing of interface access such as Application Programing Interfaces [APIs]) exist, if any, in fostering effective interoperability in this ecosystem?
- How do policy decisions by firms that operate app stores, build operating systems, or design hardware impact app developers (e.g., terms of service for app developers)?
- How do, or might, alternative app stores (other than Google Play or the Apple App Store), affect competition in the mobile app ecosystem?
- What evidence is there to assess whether an app store model is necessary for mobile devices, instead of the general-purpose model used for desktop computing applications?
- Is there evidence of legitimate apps being rejected from app stores or otherwise blocked from mobile devices? Is there evidence that this is a common occurrence or happens to significant numbers of apps?
- Are there specific unnecessary (e.g., technical) constraints placed on this ability of app developers to make use of device capabilities, whether by device-makers, service providers or operating system providers, that impact competition?
I urge American developers to send comments to NTIA, whether you’re in favour of Apple allowing real browser choice on iOS by setting Safari free, or against it. You’re welcome to use Bringing Competition to Walled Gardens, our response to a similar investigation by the UK Competition and Markets Authority for inspiration/ cutting and pasting. Make your voice heard!
- OMG let it be true: The leaked “final” version of the Digital Markets Act: A summary in ten points – “Article 5 point (e) has been expanded to capture instances where the gatekeeper requires business users to offer or interoperate with a web browser engine. This is most likely meant to address Apple’s policy of requiring all browsers running on iOS to utilize Apple’s WebKit browser engine”
- Learn PWA – A course that breaks down every aspect of modern progressive web app development
- Building a split-button component – foundational overview of how to build an accessible split-button component, by Adam Argyle
- CSS Parent Selector “In this article, I will explain the problem that :has solves, how it works, where and how we can use it with some use-cases and examples, and most importantly how we can use it today.”
- Mobile data costs fall but as demand for internet services surges, progress remains too slow – “almost one billion people live in countries where basic internet access remains unaffordable. And even in countries where 1GB is priced at less than 2% of average monthly income, income inequality means that basic internet access will still be out of reach for many lower-earners.”
- The Front-End Developer’s Guide to the Terminal by Josh W Comeau
- Designing for Children – “An evolving guide that aims to refine a new standard for both design and business to direct the development towards products and services that have ethics and children’s best interests at their core.”
- Brief Note on Buttons, Enter, and Space by everyone’s favourite Adrian.
- Download icons, logos, and vector SVGs from any site SVG Gobbler is a browser extension that finds the vector content on the page you’re viewing and gives you the option to download, optimize, copy, view the code, or export it as an image.
- Your iOS app may still be covertly tracking you, despite what Apple says – “Apple’s landmark App Tracking Transparency may not be as tough as some people think”
- Automating the accessibility tests of your source code with GitHub Actions
- Accessible Description Exposure – how and where the accessible description is exposed by assorted screen readers, by Adrian Roselli
- Cognitive Accessibility Guidance – supplemental guidance from W3C
- Staybl is a browser for Parkinson’s patients, with “customizable tremor compensation tremor compensation, high-contrast design, a particularly legible font, and general ease of use.”
- Warp – a new terminal written in Rust – looks very promising, with lots of useful features. Beta is free to download on Mac (other platforms coming)
- This is a map of America’s broadband problem – A county-by-county look at the broadband gap
- Beanstalk cryptocurrency loses $182m of reserves in flash ‘attack’ – ‘Code is law’ cryptotwats lose $182m in a manoeuvre perfectly legal according to its own code, then go sobbing to the FBI. My Decentralised thoughts and Proof of Prayers are with them in this difficult time.
- Justice Department Issues Web Accessibility Guidance Under the Americans with Disabilities Act 18 March 2022: for businesses that are open to the public (Title III): “…the ADA’s requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web”
- An anthology of insights, for a more inclusive internet – from Google’s Next Billion Users initiative
- Intent to Prototype: @scope – Scoped Styles! You can optionally provide a lower boundary so styles don’t cascade to all children
- Shifting left, or: making accessibility easier by doing it earlier – A useful slidedeck by that nice Mr @hdv about making accessibility better, and cheaper
- A Designer’s Guide to Documenting Accessibility & User Interactions an excellent article by @walterstephanie
- Apple would be forced to allow sideloading and third-party app stores under new EU law – EU: “We believe that the owner of a smartphone should have the freedom to choose how to use it, This freedom includes being able to opt for alternative sources of apps”. It’ll be interesting to see what this means for the #applebrowserban.
- Galaxy A12 is the most shipped smartphone in 2021 – The £140 Android device topped the list of 10 most shipped smartphones last year overtaking Apple
- Carousels: No one likes you – “I would like to suggest an easy alternative to adding a carousel to your page. Are you ready? Think about the content on your page”
- UA gotta be kidding – Brian Kardell on the history and lies of the humble UA string
- The Infinite Exploitation Of Cryptocurrency – “code is law”, so an attacker took $600 million of cryptocurrency from the browser-based play-to-earn blockchain game Axie Infinity, in complete accordance with the contracts involved, because Sky Mavis (the developers) had allowed them to.
- Bitcoin Failed in El Salvador. The President Says the Answer Is More Bitcoin – “plans for Bitcoin City: a new charter city to be built from scratch, centered on bitcoin mining—and powered by a volcano”