- From: Eric Eggert <ee@w3.org>
- Date: Fri, 29 Jun 2018 10:27:48 +0200
- To: "Wayne Dick" <wayneedick@gmail.com>
- Cc: public-low-vision-a11y-tf@w3.org
- Message-ID: <D8683942-E5D6-44BC-A44D-0DED464D5026@w3.org>
Hi Wayne, I just rolled out a fix for the bug. It was me using grid wrong. I found the issue yesterday but didn’t have enough time to validate and roll out a fix. You might need to force your browser(s) to reload the CSS, the W3C server can be very insisting on caching it. Basically I used a grid layout (that should not have been used on small screens) which broke the layout on the home page. It was hard to notice when not modifying the font. I fixed it by not applying the grids, as was the initial plan: https://github.com/w3c/wai-website-components/commit/40aa73853b0fb2a655464a30eb2eba0465308300 I also fixed the menu button positioning on small viewports to work with the modification. ([commit]) I’m looking into changing the menu button and workflow to better work with the submenus that we introduced. (Open issue [#76].) I don’t think this lends itself to a technique (apart from: don’t write bugs 😉). Thanks again for reporting the bug, we want to implement best practices on WCAG 2.1 as much as we can within our possibilities. Fixing this bug shows that it is possible to have a small viewport and a layout that adapts reasonably to text modifications by the user. Best, Eric [commit]: https://github.com/w3c/wai-website-components/commit/8760324df07420b4086242a699f43307a4d08612 [#76]: https://github.com/w3c/wai-website/issues/76 -- Eric Eggert Web Accessibility Specialist Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
Received on Friday, 29 June 2018 08:27:53 UTC