Warning: Patrick looms large in various discussions
I have been meaning to start a periodic noting of meaty articles and threads related to subjects close to my technical heart. Today intent meets action. Here’s a few that have tickled my fancy of late:
- Semantics to Screen Readers – great introduction to assistive tech (AT)/browser accessibility API topic. Also see Accessibility APIs: A Key To Web Accessibility
- Short note on scoping mechanisms – The need for and required use of the
scopeattribute is overplayed…
- HTML5 Landmarks Exposed – Current reality of HTML ‘landmark’ semantics support across browsers and AT.
- How do You Test Success Criterion 1.3.5 on Mobile Applications? – Can it be tested? Is it applicable to native mobile? Best Practice vs WCAG 2.1 Conformance. Related discussions:
- Use of
@stevefaulkner Do you know any resources for making <object> accessible? I was toying with using it for its fallback HTML for cases where `alt` is insufficient, like comics
— Taylor Hunt (@tigt_) May 14, 2019
- 1.4.4 – Clarification needed for Success Criterion for mobile browsers – Discussion on mobile browsers and text resizing
- Thread: Placeholder and Accessible Name Computation – Just because we don’t like something, we can’t spec it away.
- There was recently a splash, grump and kerfuffle about about Google’s promotion of a new (experimental) HTML element by the name of
portalI subsequently had a gander at it: Short note on the portal element
That’s almost it for #1, but first a question: feel free to provide your answer as a comment on this article.