#wpfooter unavailable on 200% zoom (WCAG 1.4.10 Reflow (Level AA))

[alh0319]

There is CSS that intentionally hides #wpfooter on mobile.

@media screen and (max-width: 782px) {
    #wpfooter {
        display: none;
    }
}

The footer holds important information about the current WordPress version and can be extended by themes and plugins to hold other important links or information.

If a user has low vision and is zoomed in 200% or more, they do not have access to any information in the footer. This is a failure of ​WCAG 1.4.10 Reflow (Level AA).

How to test:

1. Set your browser width to 1280 CSS pixels wide.
2. Go to the main dashboard page in the admin.
3. Zoom your browser and observe that the footer disappears.

The footer should stay visible up to 400% zoom, which can be achieved by removing this CSS.

[abcd95]

Introduced in [26134]

Perhaps we can also improve the look and feel of the footer once this is agreed upon -

src/wp-admin/css/common.css

@@ -4221 +4221 @@
         }
 
         #wpfooter {
-                margin-left: 0;
+                display: flex;
+                flex-wrap: wrap;
         }
 
         #comments-form .checkforspam {

[alh0319]

I like the stacked and left align. Thank you!

Please do not switch the footer display to flex on a bugfix ticket.

• With only display: flex and flex-wrap: wrap, the two default paragraphs can stack nicely in a development version, where one of the paragraphs is very wide. However, most sites would have shorter paragraphs running together on the left.
• In theory, the footer could also have justify-content: space-between, but then the #wpfooter .clear div would need to be hidden or removed.
• Plugins can add anything before these two paragraphs with the in_admin_footer action. A directory search found ​160 plugins that use the hook in some way. This shows an extra div with flex, wrap, and space-between:

Please do not switch the footer display to flex on a bugfix ticket.

Thanks for the detailed note. To clarify, the display: flex suggestion wasn't something I was pushing for in this ticket. I mentioned it purely as an aside, as a possible future improvement to footer layout. I fully agree it's outside the scope here, and the edge cases you illustrated make it a more carefully scoped undertaking.