This site commits to WCAG 2.2 AA as its accessibility target. That means readable text contrast, keyboard navigation on every interactive element, meaningful alternative text where images appear, visible focus indicators, and semantic structure that assistive technology can navigate.
The exchangelogin.gr.com reference site is built to be usable by the widest possible range of readers, including people who rely on screen readers, keyboard-only navigation, high-contrast themes, or magnification. The stated conformance goal is the Web Content Accessibility Guidelines 2.2 at the AA level, the standard most government references and most member-facing banking references work toward.
The page structure uses semantic HTML — section, nav, header, footer, article, and heading levels — so assistive technology can read the page as the author intends. Every interactive element is reachable by keyboard with a visible focus outline. Text color contrast meets at least 4.5 to 1 on regular-weight text and 3 to 1 on large text. The reading order matches the visual order, which keeps a screen-reader experience consistent with a visual one. The mobile layout reflows at 320 pixels without loss of content or functionality.
The site has been built against modern combinations of operating system, browser, and screen reader — current releases of NVDA with Firefox, JAWS with Edge, and VoiceOver with Safari. Where native controls are used, the built-in role, name, and state exposed by those controls is preserved. No custom JavaScript widget replaces a semantic element that the platform already exposes correctly.
This statement covers the pages of exchangelogin.gr.com. The Exchange Bank sign-in experience, online banking, and mobile banking apps are operated by the bank on different domains and are governed by the bank's own accessibility commitments. Nothing on this reference site replaces or represents those.
A small set of limitations is known. First, the site uses CSS gradient fills rather than raster images for decorative background sections, which reduces the need for long alternative text but removes some editorial imagery. Second, color-coded status labels inside tables pair the color with a text label, yet some tables remain text-heavy on smaller screens and benefit from landscape orientation on a phone. Third, the font stack loads a remote webfont from Google Fonts; readers who block third-party font loading still receive a readable system-font fallback.
| Feature | Status | Standard |
|---|---|---|
| Semantic landmarks | Implemented | WCAG 2.2 · 1.3.1 |
| Keyboard navigation | Implemented | WCAG 2.2 · 2.1.1 |
| Visible focus outline | Implemented | WCAG 2.2 · 2.4.11 |
| Text contrast | Meets AA | WCAG 2.2 · 1.4.3 |
| Reflow at 320 px | Implemented | WCAG 2.2 · 1.4.10 |
| Language of page | Declared en | WCAG 2.2 · 3.1.1 |
| Page titles | Unique and descriptive | WCAG 2.2 · 2.4.2 |
| Link purpose | Descriptive link text | WCAG 2.2 · 2.4.4 |
| Non-text content | CSS gradients only | WCAG 2.2 · 1.1.1 |
| Consistent navigation | Header persists | WCAG 2.2 · 3.2.3 |
Readers who encounter a barrier — a page that does not read aloud cleanly, an interactive element that does not take keyboard focus, a contrast problem that hurts readability — can write through the channel on the contact reference. Feedback is reviewed promptly, and fixes are rolled out in the normal publishing cadence of the site. When a reader asks for content in an alternate format, the site will make a reasonable effort to provide it.
Federal guidance on digital accessibility is at the ADA.gov web accessibility guidance, which is a useful reference for readers evaluating any public-facing website. The FTC consumer advice on personal information pairs well with this statement because accessibility and privacy belong in the same conversation about a calm reading experience.
The site updates this statement when material accessibility changes ship. The revision date in the eyebrow reflects the most recent review. Readers are welcome to reach out for specific conformance information about a particular page at a particular point in time.
The reference home is index. Legal siblings include the privacy policy and the terms of service. Security content lives at the security center. Access explainers are at the exchange bank login reference and the login help-guide, and the contact reference carries the feedback channel mentioned above.
The site targets the Web Content Accessibility Guidelines 2.2 at the AA level. That is the same benchmark used by most government digital properties and by most member-facing banking references.
Write through the channel on the contact reference with the URL of the page, a description of the barrier, the assistive technology in use, and a brief example. Fixes are rolled out in the normal publishing cadence.
No. The bank's sign-in experience, online banking, and mobile banking apps are operated by the bank on different domains and are covered by the bank's own accessibility commitments. This statement covers only exchangelogin.gr.com.