Accessibility Statement
- Document reference
- FGL-LEG-18
- Version date
- 1 July 2026
- Applies to
- Fratres Limited
1.Interpretation and definitions
In this Accessibility Statement the following capitalised terms bear the meanings given to them below. Terms defined in the Web Content Accessibility Guidelines and not otherwise defined here bear the meanings given to them in that document.
- Company
- Fratres Limited, a private company limited by shares incorporated and registered in England and Wales, being the operator of the Website.
- Website
- The website published at fratresgroup.com, together with every subdomain, sub-directory and page operated by or on behalf of the Company under that domain.
- Statement
- This Accessibility Statement, as amended and republished from time to time in accordance with clause 16.
- WCAG
- The Web Content Accessibility Guidelines published by the World Wide Web Consortium. References in this Statement to WCAG are references to version 2.2 unless a different version is expressly identified.
- Level AA
- The intermediate of the three conformance levels defined by WCAG. Conformance at Level AA requires that every Level A and every Level AA success criterion is satisfied, or that a conforming alternative version is provided.
- Success Criterion
- An individual, testable requirement stated in WCAG, cited in this Statement by its numeric reference and title.
- EN 301 549
- The harmonised European standard setting accessibility requirements for information and communication technology products and services, which incorporates WCAG at Level AA as the requirement applicable to web content.
- Assistive Technology
- Hardware or software that a person uses to perceive, operate, understand or interact with the Website, including screen reading software, screen magnification software, speech recognition software, switch access devices, refreshable braille displays and alternative pointing and keyboard devices.
- Accessibility Barrier
- Any feature, omission or behaviour of the Website which prevents or makes unreasonably difficult the perception, operation or understanding of the Website by a person, whether or not that feature also constitutes a failure of a Success Criterion.
- Alternative Format
- A version of content published on the Website supplied by a different means or in a different form, including structured plain text, large print, or a document prepared for use with Assistive Technology.
- Reasonable Adjustment
- A step required to be taken under sections 20 and 29 of, and Schedule 2 to, the Equality Act 2010 to avoid a substantial disadvantage to a disabled person arising from a provision, criterion or practice, or from the absence of an auxiliary aid.
- Enquiry Form
- The enquiry form published at fratresgroup.com/contact, being the sole channel through which the Company receives enquiries and reports from the public.
- Business Day
- Any day other than a Saturday, Sunday or public holiday in England and Wales.
- Visitor
- Any person who accesses the Website, whether or not that person subsequently makes an enquiry or enters into any relationship with the Company. References in this Statement to “you” are references to the Visitor.
2.Purpose, scope and status
3.The standard targeted
- (a)the stated conformance level must be satisfied in full, no partial claim being permitted;
- (b)conformance is claimed for full pages, and not for parts of pages;
- (c)where a page forms one step in a process, every page in that process must conform, so that a person is not stranded partway through;
- (d)only accessibility-supported ways of using technologies may be relied upon to satisfy a Success Criterion; and
- (e)technologies which are not relied upon must not interfere with the ability to access the rest of the page.
4.Legal framework
This Statement is not a certification and is not an audit report. It records the Company’s own assessment of the Website against WCAG 2.2 at Level AA, including the respects in which the Website does not presently meet that standard. Clause 12 explains how that assessment is made and what weight it should be given.
5.Structure, semantics and navigation
- —The document language is declared as British English on the root element of every page, so that speech synthesis selects the correct pronunciation rules.
- —Each page carries exactly one first-level heading, and subordinate headings descend in order without levels being skipped. Headings are real heading elements; no text is made to look like a heading by styling alone.
- —Each page is divided into landmark regions — a banner, a single main region, a content-information footer and navigation regions — so that a person using Assistive Technology may move directly between the parts of the page.
- —Where more than one navigation region appears on a page, each carries a distinct accessible name. On the pages of the legal register the clause index is exposed as a navigation region named “Contents”.
- —Lists are marked up as lists, ordered where the order carries meaning and unordered where it does not. The clause index and the numbered process sequences are ordered lists; definition tables are description lists with paired terms and descriptions.
- —A “Skip to content” link is the first element to receive focus on every page. It is visually hidden until focused, becomes plainly visible on focus, and moves focus to the start of the main region.
- —Anchored links within a document account for the height of the fixed navigation bar, so that a clause heading reached from the contents index is not concealed beneath it.
- —Every page carries a unique and descriptive title, formed from the page name and the name of the Company, so that a page can be identified from a browser tab, a history entry or a list of open windows.
- —Purely presentational marks — the em rule that precedes each bulleted item, the arrow glyph on a link, the menu icon and the oversized vertical wordmark on photographic headers — are hidden from Assistive Technology so that they are not announced as content.
6.Keyboard operability and focus
- (a)the control which opens it is a button which reports whether the overlay is open and which identifies the element it controls;
- (b)the overlay is exposed as a modal dialogue with an accessible name;
- (c)focus is moved into the overlay when it opens;
- (d)tabbing cycles within the overlay while it is open and does not escape into the page behind it;
- (e)the Escape key closes the overlay from anywhere within it, and a visible close control is also provided;
- (f)focus is returned to the control which opened the overlay when it closes; and
- (g)the scroll position of the underlying page is preserved and restored.
7.Colour, contrast and visual presentation
- —Primary body text, headings and clause numbering are set in the dark bark tone on the cream page, measuring approximately 11.8 to 1. This substantially exceeds the 4.5 to 1 required by Success Criterion 1.4.3 Contrast (Minimum) and also exceeds the 7 to 1 required at Level AAA.
- —Secondary body text, used for definitions, descriptions and supporting paragraphs, is set in the mid earth tone, measuring approximately 4.7 to 1 and satisfying Success Criterion 1.4.3 for text at any size.
- —The single primary action on any view is white text on deep teal, measuring approximately 9.6 to 1. Outlined secondary actions are dark bark text on cream at approximately 11.8 to 1.
- —The focus indicator is deep teal, measuring approximately 9.1 to 1 against the cream page.
- —The skip link, when focused, is white text on deep teal at approximately 9.6 to 1.
- —The exception is the light grey tone used for captions, metadata and hint text, which is recorded as a non-conformance at clause 11.2.
8.Motion, animation and resilience
- (a)a global stylesheet rule reduces the duration of every animation and every transition to an imperceptible interval, disables smooth scrolling and renders revealed content immediately visible; and
- (b)the script which observes content entering the viewport queries the same preference and, where it is set, marks all content visible at once without observing anything or running any animation.
9.Text alternatives and non-text content
10.Forms, labelling and error handling
- (a)each field in error is identified programmatically as invalid;
- (b)a message in plain language is placed beneath the field, associated with it so that it is announced with the field, and the message states how to correct the problem rather than merely stating that a problem exists;
- (c)a summary appears at the head of the form listing every field in error, each entry being a link which moves focus to the field concerned;
- (d)focus is moved to the first field in error, so that a keyboard user is placed at the problem rather than having to hunt for it;
- (e)the number of fields requiring attention, and the fact that nothing has been submitted, are announced through a polite live region which does not interrupt anything already being read; and
- (f)once a submission has been attempted, validation runs again as values change, so that messages clear as problems are corrected rather than persisting until the next submission.
11.Known limitations and non-conformances
The limitations at clauses 11.2, 11.3 and 11.4 are contrast defects in the design system rather than defects in individual pages. Each is corrected by changing the value of a single design token, and each correction applies across the whole Website at once. They are scheduled for the next revision of the design system and are treated as defects rather than as design decisions.
12.Assessment approach and basis of claim
- —traversal of every page template using a keyboard alone, without a pointing device, confirming that every function can be reached, operated and left, and that the focus position is discernible at each step;
- —operation of every page template with screen reading software, confirming that headings, landmarks, lists, labels, states and error messages are announced correctly and in a sensible order;
- —inspection of the accessibility tree rendered by the browser, to confirm that the structure exposed programmatically matches the structure presented visually;
- —measurement of the contrast ratio of every colour pairing used in the design system for text and for user interface boundaries, calculated against the relative luminance formula stated in WCAG rather than estimated by eye;
- —automated rule-based scanning, used to catch regressions of a mechanical kind and never relied upon as evidence of conformance, since automated tooling detects only a minority of accessibility defects;
- —rendering at increased zoom levels and at narrow viewport widths, confirming that content reflows without loss of information or function and without horizontal scrolling;
- —rendering with scripting unavailable, confirming that the substance of every page remains present and readable; and
- —rendering with a reduced-motion preference set, confirming that animation is suppressed.
13.Reporting an accessibility barrier
- —the address of the page concerned, or a description sufficient to identify it;
- —what you were attempting to do;
- —what happened instead, and at what point the difficulty arose;
- —the browser, operating system and Assistive Technology in use, with version numbers if they are known; and
- —whether you were able to complete the task by some other route.
- (a)whether the matter reported is accepted as an Accessibility Barrier and, if so, which Success Criterion is affected;
- (b)what the Company intends to do about it and by when;
- (c)where remediation is not to be undertaken, the reason; and
- (d)what alternative means of obtaining the content or completing the task is available in the meantime.