Interface basics
The shared public-page layout provides a skip-to-content link and identifies the site language as English. Page templates use headings, landmarks and lists so assistive technology receives meaningful structure rather than presentation alone.
Shared focus styles give keyboard-operated links, buttons, fields and disclosures a three pixel outline in the site accent color. The main navigation menus, search palette, Ask Metro Power panel and motion panel are designed to contain focus while open, close on the Escape key and return focus to their opening control. These behaviors are checked on representative journeys during release review.
The site form components are designed around visible labels and named controls. Decorative images use empty alternative text so assistive technology can skip them, while informative images are expected to carry a useful text alternative. Release checks look for missing names and image alternatives across the rendered route set.
Text, contrast and control size
The site sets three numeric floors and builds interface copy to them rather than to whatever a component happened to inherit. Section 08 states the limits of that.
- Smallest text
- The current design target is 11 pixels for a technical label, 12 pixels for a note, 13 pixels for compact copy and 16 pixels for body copy on reading pages such as this one. Automated reviews flag rendered text below the applicable target so older and newly rebuilt surfaces can be corrected.
- Contrast
- Text colors come from one fixed palette. The lightest pairing in it, gray text on the paper ground, measures 5.4 to 1, and most pairings measure above 7 to 1, against the 4.5 to 1 that WCAG AA asks for normal text.
- Control size
- New and rebuilt buttons, filters, tabs and checklist rows target at least 44 pixels of height and usually 48. Checkboxes and radio buttons remain visually compact, so their surrounding labels are intended to provide the larger touch target.
- Zoom
- Phone form fields target a 16 pixel text size to avoid unwanted browser zoom. Representative mobile routes are checked for horizontal overflow, and responsive layouts are corrected when content exceeds the viewport.
A link inside a sentence, including the email and telephone links on this website, is the height of the text around it and not 44 pixels. WCAG 2.5.8 exempts inline text links for that reason. Where an action matters, such as reporting a problem with this page, it is given a full-size button instead of an inline link.
Motion
Motion on this site explains a system relationship or a change of state. It is never the only way something is communicated, and no page requires you to watch an animation to reach the information.
If your device or browser is set to reduce motion, the site follows that setting: animation and transition are switched off rather than shortened. You can also override the device setting for this site alone. The motion control in the footer offers three choices, follow the device, reduce movement, or use full movement, and your choice is kept in your own browser on that device.
Captions and transcripts
Metro Power hosts 35 Visual explainers itself. Every one of the 35 ships with an English caption track that the player turns on from its own controls, and with a full text transcript you can read instead of watching. The transcript link is also the fallback shown if your browser cannot play the video at all.
Four short explainer videos published by other companies are embedded inside Academy courses. Those four load from YouTube's no-cookie domain, and only after you press play, so nothing is requested from YouTube while you are just reading the lesson. Their captions and player controls belong to the publisher, not to Metro Power, and the surrounding lesson always carries the same point in text.
Technical content and diagrams
Architecture drawings, single-line diagrams and product illustrations are always accompanied by the explanation in text. Long technical papers and lessons carry a section index, and remember where you stopped reading on that device so you do not have to find your place again.
The learning path does not depend on any video, any diagram or any planning tool. Every Academy path can be completed by reading.
Forms and documents
The project request flow uses explicit labels, marks required fields in the label itself, provides text error guidance and is designed for keyboard operation. If a submission cannot be recorded, the interface is intended to explain the problem and provide a telephone route instead of failing silently.
If a technical document cannot be attached through the website, for any reason including an accessibility one, send it by email or call the office and Metro Power will arrange another intake route. A request made that way is recorded the same way as one made through the form.
How each release is checked
Before a release, automated and manual checks cover representative desktop, tablet and phone journeys. They examine keyboard reachability and focus order, visible focus, form labeling, heading structure, accessible names, rendered text size, control size, horizontal overflow, console errors and failed requests. Interactive tools are sampled in both empty and completed states, where different faults can appear.
The site also records anonymous loading and responsiveness measurements, grouped only by broad device width, so real visitor experience rather than a laboratory score guides what gets fixed. The privacy notice sets out exactly what those measurements contain.
What this statement does not claim
No page or service on this website has been independently certified against any accessibility standard, and Metro Power does not claim conformance on behalf of any third party.
The floors in section 02 are the standard the site is built to. They are not a measurement of every screen, and the date on this statement is the date the statement was written, not a date on which the whole site was certified against them. A screen that has just been built or rebuilt is the one most likely to be behind. Release checks measure rendered text and control size route by route, and anything found below a floor is raised in the next release rather than left in place.
Metro Power does not control the four embedded third-party videos, the transcripts of documents supplied by principals, or the behavior of a browser extension or assistive tool a visitor uses. Checks are practical and repeated at every release, not exhaustive: they cover representative journeys rather than every state of every page, and they do not include screen reader listening tests.
Where a fault is found after a release, it is recorded and prioritized for the next appropriate correction cycle. If you found it, please tell us, because a reported barrier can be reproduced and addressed faster than an undiscovered one.
Metro Power website accessibility statement. Reviewed at every website release; the date above is the last substantive revision.