![]() ![]() … but now programmatically determinable becomes important for user groups: cognitive, voice control … in past many assumed closed means closed to screen readers, so app must provide own speech GreggVan: heads up on closed functionality, problem that all the standards have, we'll see in ANPRM from Access board but for now we're the first standard tackling … similar analysis is going on for text and command line applications … looking to touch base with contributors on Problematic for Closed Functionality section, between our weekly calls … we should now concurrently work on 2.1 open issues, looking for owners for a few issues Maryjom: progress board is now up to date, showing AGWG progress and current tasks in progress in our task force There's a lot of AAA, and it will take a while to get through them all. I don't think we can do that along with the current round of updates. mitch11: the publication process doesn't preclude going back to AGWG? It will take us enough time to get A and AA done for EN 301 549. None of the regulatory standards require AAA. maryjo: AAA is not in the timeline, it will have to be later. … so we focus on remaining work items of above items Mary Jo working with Michael on technical parts … appendix on criteria problematic for closed functionality, aiming for June 30 to AGWG and publication process, leading to publishing in July this timing might be at risk … text-based interfaces appears on track for June Maryjom: progress slower than expected on Reflow Link to schedule and milestones: / w3c/ wcag2ict/ wiki/ Schedule-and-milestones w3c/ wcag2ict/ wiki/ Scribe-list-&-instructions Announcements Discussion on definition of Device-independent pixels.Exploring WCAG 2.1: 1.4.Attendees Present ChrisLoiselle, Chuck, Daniel, Devanshu, FernandaBonnin, GreggVan, lmiller, maryjom, Mike_Pluke, mitch11, olivia-hs, Sam, shadi Regrets Bruce Bailey, Shawn Thompson, Thorsten Katzmann Chair Mary Jo Mueller Scribe mitch11 Contents.Technical guidance is available for implementing this Success Criterion at the Understanding Success Criterion 1.4.10: Reflow page. Set horizontal scrolling content at a height equivalent to 256 CSS pixels.Set vertical scrolling content at a width equivalent to 320 CSS pixels.Note: This success criterion does not apply to content that requires a two-dimensional layout (e.g. Zoom to 400% without requiring the user to scroll horizontally or vertically.So that I can complete my assignments when commuting to school.Įnsure content on your site or application is designed to: I want to view content without scrolling back and forth So that I can interact with everything on the page.Īs a person who reads textbooks on my phone, I want to have the content readjust to fit the screen This makes it easier to read content and track lines of text.Īs a person with low vision who sets my browser zoom to 400%, When browser zoom is used to enlarge content up to 400%, the content should wrap or reflow to one column, so users do not have to scroll in more than one direction. When sites or applications are not responsive, users must scroll back and forth to reveal lines of text and at times text may be hidden off screen.Ī responsive site or application helps all people using various devices and especially supports those with low vision that require enlarged text. ![]() When content in your site or application is zoomed up to 400%, does text wrap into one column so scrolling is not required in more than one direction? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |