1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: (Level AA) • Vertical scrolling content at a width equivalent to 320 CSS pixels; • Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. These 2 requirements are to be met simultaneously and are not independent of each other. A user should be able to increase the size of text to 200% even when the information is displayed on a narrow mobile phone screen. Alternatively, a user should be able to magnify the screen to 400% and increase the text size a further 200% Users with visual impairments often enlarge web content to make it easier to see. When content is enlarged to 400% zoom or viewed on a screen with a width of 320 CSS pixels, content should be presented to a user with no loss of information or functionality, and without requiring scrolling in two dimensions. The value of 320 CSS pixels was chosen as a reasonable minimum size that authors could achieve and also replicates the smaller screen sizes of common mobile devices. The width of 320 CSS pixels exactly corresponds to a desktop browser window set to a width of 1280px and zoomed in to 400%. FAIL: When the browser window is set to a width of 320px on the homepage, the horizontal scroll bar is displayed. FAIL: When the browser window is set to a width of 320px on the ‘Details for: Biblio title’ page, the horizontal scroll bar is displayed. Other pages may also be failing on this criteria.. To reach AA standard, we are required to rework these pages and how they reflow for such zoom levels/screen sizes.
We have recently reviewed our accessibility statement and we have noticed this issue on the search results page of our OPAC. Users should be able to enlarge/zoom up to 400% without loss of function. However, when display is set to 1280x wide, looking at the search results page, we find that a user can’t enlarge above 200% before the search results header obscures everything on the page, so the search results aren’t visible. This fails WCAG 2.1 criterium 1.4.10. We have noted this as an issue in our accessibility statement and would like to see this improved in order to comply with WCAG standards.
(In reply to Georgia Newman from comment #1) > We have recently reviewed our accessibility statement and we have noticed > this issue on the search results page of our OPAC. Users should be able to > enlarge/zoom up to 400% without loss of function. However, when display is > set to 1280x wide, looking at the search results page, we find that a user > can’t enlarge above 200% before the search results header obscures > everything on the page, so the search results aren’t visible. This fails > WCAG 2.1 criterium 1.4.10. We have noted this as an issue in our > accessibility statement and would like to see this improved in order to > comply with WCAG standards. Hi Georgia! Thanks for reporting this. These bugs are meant to be "Omnibus" bugs, meaning that we keep them open and link other bugs to it that solve individual issues around the topic. I have moved your comment into a new bug report: Bug 36471 - Accessibility: OPAC search results header obscures content when zooming in Please feel free to add or refine it!