Accessibility
What has been done to keep this usable with a keyboard, a screen reader and at a large text size — and how to tell us where it falls short.
What has been done
The site is built as ordinary HTML with a single main heading per page and headings in order below it, so a screen reader’s outline matches what is on the screen. Every control in the checker has a real label tied to it rather than placeholder text standing in for one.
Everything works with a keyboard alone, and focus is visible as it moves. Nothing depends on hovering, and nothing requires a pointer.
Colour is not used as the only way of conveying anything, and text contrast is chosen to stay legible rather than to look faint. Layout is responsive and reflows down to a narrow screen and up to a large text size without content being cut off or requiring horizontal scrolling.
The tables
Where a page lists codes in a table, it is a real table with real column headers, so it can be navigated cell by cell. Wide tables scroll within their own region instead of forcing the whole page sideways.
Where it may fall short
This has not been audited against the Web Content Accessibility Guidelines by a third party, and no claim of conformance to a particular level is made here. Automated checks catch structural problems; they do not prove a page is usable.
Telling us
If something here does not work with your assistive technology, that is a defect and worth reporting. Say which page, what you were using, and what happened.
The figures and rules on this site are taken from the Income Tax (Pay As You Earn) Regulations 2003, the Income Tax Act 2007 and HMRC’s published guidance, and are shown as they were found. They have not been signed off by a reviewer. Where the law and HMRC’s naming differ, the page says which is which rather than blending them. For anything that affects a decision, the cited document governs and this site does not.