Logistics
Facilitator(s)
daniel-montalvo
Summary
Some requirements under the Web Content Accessibility Guidelines (WCAG) are no longer needed because browsers are able to compensate authoring errors that used to create accessibility barriers.
For example, WCAG 2.2 has now removed the requirements around start and end tags, unique ids, and appropriate element nesting. Some browsers already include settings to improve focus visibility, which greatly help keyboard users when web authors don't provide accessible enough focus indicators.
But there is still progress to be made for current accessibility requirements to be remediated at the rendering stages to make accessibility easy to implement. We will walk through some of the most obvious (and not so obvious) ones, from the perspective of WCAG.
Type
Onsite
Other comments
No response
Logistics
Facilitator(s)
daniel-montalvo
Summary
Some requirements under the Web Content Accessibility Guidelines (WCAG) are no longer needed because browsers are able to compensate authoring errors that used to create accessibility barriers.
For example, WCAG 2.2 has now removed the requirements around start and end tags, unique ids, and appropriate element nesting. Some browsers already include settings to improve focus visibility, which greatly help keyboard users when web authors don't provide accessible enough focus indicators.
But there is still progress to be made for current accessibility requirements to be remediated at the rendering stages to make accessibility easy to implement. We will walk through some of the most obvious (and not so obvious) ones, from the perspective of WCAG.
Type
Onsite
Other comments
No response