W3C home > Mailing lists > Public > public-apa@w3.org > December 2019

Re: HTML Accessibility Review

From: Janina Sajka <janina@rednote.net>
Date: Wed, 18 Dec 2019 08:52:26 -0500
To: Matthew Tylee Atkinson <matkinson@paciellogroup.com>
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>, Léonie Watson <lwatson@tetralogical.com>, Xiaoqian Wu <xiaoqian@w3.org>
Message-ID: <20191218135226.GC2805@rednote.net>
Hi, All:

A brief update from Accessible Platform Architectures (APA) regarding
the HTML review by Matthew ...

We're pleased Matthew was able to perform a thorough review on our
behalf. We've discussed his finding on several successive APA
teleconferences. While Matthew has, in our view, correctly noted certain
issues that would benefit accessibility, none rises to the level of a
major blocking concern for APA.

My apologies for the late notice here, but I thought it better to
respond late than not at all.

The best of year end hollidays to all!

Janina Sajka, Chair
Accessible Platform Architectures (APA) Working Group

Matthew Tylee Atkinson writes:
> Hi all,
> Quick update: last week, I filed an issue about focusing and the <audio> and <video> elements [0]; two things arose:
> 1. I misunderstood that by taking the <audio> and <video> elements out of the default tabindex, they're not necessarily saying that means that they shouldn't be focusable, but at the confusion arose, we are working on clarifying things in the spec.
> 2. I gather WHATWG feels it's not a good idea to specify whether <audio> and <video> (and specifically when there are embedded controls) should be focusable or not, as the browsers vary on this, so there’s not really consensus yet. I’m not sure if the browsers that /don’t/ have them in the focus order use the “container” approach suggested by Joanmarie in our call last week [1].
> I did spot what seemed like several keyboard accessibility issues with current implementations, so maybe a couple of us could try things out and report browser bugs where needed, and then maybe eventually we'll get to a situation where there's a cowpath to be paved, but regardless of that, and more importantly, the accessibility of these elements in general would improve. However I am low on cycles, so this can't be a fast activity for me. I can keep APA updated if I am able to make any progress in future, though, and if anyone would like to help, please let me know.
> I've not yet filed the previously-discussed issue on HTML about adding an accessibility warning to the 'pop-up opener navigation' example, but still intend to (the above one took precedence). It's definitely not urgent, and shouldn't hold the publication process up.
> best regards,
> Matthew
> [0] <https://github.com/whatwg/html/issues/5087>
> [1] <https://www.w3.org/2019/11/13-apa-minutes.html#item05>
> -- 
> Matthew Tylee Atkinson
> --
> Senior Accessibility Engineer
> The Paciello Group
> https://www.paciellogroup.com
> A Vispero Company
> https://www.vispero.com/
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.


Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 18 December 2019 13:52:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:55:36 UTC