SL-SAG LogoSL-SAG

Accessibility Statement

Draft

This document is a working draft and is pending formal legal review. It may change before being finalized. Questions? Contact us at support@slsag.org.

SL-SAG — Somaliland Strategic Advisory Group Last updated: May 2026 Version: 1.0-draft

Our commitment

SL-SAG is committed to making slsag.org accessible to everyone, including people with disabilities. We want our policy analysis and research to be readable by all who need it, regardless of how they access the web.

Our target is compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines, published by the World Wide Web Consortium (W3C), cover the main barriers that prevent people with disabilities from accessing web content.

We recognise that accessibility is ongoing work, not a one-time task. We review the site regularly and fix problems as we find them.

What we have done

The following measures have been taken to improve accessibility:

Structure and navigation

  • Pages use a logical heading structure (H1 → H2 → H3) so screen readers can navigate by heading.
  • All pages have a descriptive page title and a clear main landmark region.
  • Keyboard navigation works throughout the public site and the contributor portal: all interactive elements (links, buttons, form fields) are reachable and operable using a keyboard alone.
  • A "skip to main content" link is provided at the top of each page for keyboard users.

Text and readability

  • Body text is set at a minimum equivalent to 16px.
  • Colour contrast between text and background meets or exceeds the WCAG 2.1 AA ratio of 4.5:1 for normal text and 3:1 for large text.
  • Text can be resized up to 200% in the browser without loss of content or functionality.
  • We avoid using colour alone to convey information.

Images and media

  • All meaningful images have descriptive alternative text (alt text).
  • Decorative images are marked so that screen readers skip them.
  • Any embedded charts or data visualisations include a text description or accessible data table as an alternative.

Forms

  • All form fields (contact form, newsletter signup, contributor portal) have visible labels.
  • Error messages identify the field concerned and describe what the user needs to do.
  • Required fields are clearly marked.

Links

  • Link text is descriptive. We avoid links labelled only "click here" or "read more."

Documents

  • Where possible, reports and briefings are available as accessible PDFs (tagged, with reading order set). Older documents may not meet this standard.

Known limitations

We have identified the following areas where accessibility is not yet fully achieved:

  • Older PDF reports: Documents published before the current site was built may not be fully tagged for screen reader access. We are working through the archive and will prioritise the most-accessed documents.
  • Complex data tables in long-form reports: Some embedded tables in older articles do not have full header-row markup. This is being addressed in ongoing content updates.
  • Video content: If video is added to the site, captions and transcripts will be provided. At the time of publication, no video content is hosted.

If you encounter a barrier not listed here, please let us know (see "How to report a problem" below).

Technical information

slsag.org is built using modern web technologies including HTML5, CSS, and JavaScript. The site is designed to be compatible with the following assistive technologies, based on current usage data:

  • Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
  • Browser and OS zoom
  • High-contrast display modes

We aim for the site to be usable without JavaScript for core reading and navigation functions.

Compliance status

We believe slsag.org is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not fully conform, as described in "Known limitations" above. We are working towards full conformance.

[Note to tobbi: if a formal WCAG audit has been conducted, replace the above self-assessment with the audit date, auditor, and audit findings summary.]

How to report a problem

If you find a part of slsag.org that you cannot use because of an accessibility barrier, we want to hear about it.

Email us at support@slsag.org with "Accessibility" in the subject line. Please describe:

  • What you were trying to do
  • What happened instead
  • The page URL where the problem occurred
  • The browser, operating system, and assistive technology you were using (if known)

We aim to respond within five business days and to fix confirmed accessibility issues within 30 days for high-priority barriers.

Formal complaints

If you are not satisfied with our response to your accessibility report, you can raise the matter with the relevant body in your country. In the UK, this is the Equality and Human Rights Commission (EHRC). In the EU, your national enforcement authority handles complaints under the European Accessibility Act.

Requesting content in an alternative format

If you need a specific report or article in an alternative format (for example, large-print, plain text, or as a document compatible with your screen reader), contact support@slsag.org. We will try to provide an alternative within ten business days.

Review schedule

This statement was prepared in May 2026. We review it at least once a year and after any significant change to the site's design or functionality.

Notes for internal review:

  1. This statement is a self-assessment. For credibility — especially if SL-SAG seeks partnerships with international donors or institutions — commission a formal third-party WCAG audit and update this statement with the auditor's findings and date.
  2. The European Accessibility Act (EAA) applies to certain organisations providing services to EU consumers, with most obligations applying from June 2025. An attorney should confirm whether SL-SAG is within scope.
  3. If slsag.org receives UK public funding or serves UK public bodies, the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 may impose additional requirements, including the mandatory publication of an accessibility statement in a specific format.
  4. The PDF accessibility note should be revisited once the Payload CMS export pipeline is confirmed — if PDFs are generated programmatically, it is easier to build in accessibility from the start than to retrofit.