Skip to main content
Standing with Sudan: Support communities affected by conflict and displacement. Support the response
TUSIC The United Sudanese International Council
Donate

Inclusive access

Accessibility Statement

TUSIC seeks to make its website and digital information usable by as many people as reasonably possible, including people with disabilities who use assistive technologies.

Accessibility target WCAG 2.2 Level AA
Statement issued [MONTH DAY, YEAR]
Last reviewed [MONTH DAY, YEAR]
Current status: WCAG 2.2 Level AA is TUSIC’s target. Full conformance should not be claimed until the production website has been independently or appropriately evaluated.

Found an accessibility barrier?

Tell us what prevented you from using the website

Describe the page, content or feature and the format or assistance that would help you.

Report a barrier

01

Our accessibility commitment

[FULL LEGAL NAME OF TUSIC ENTITY] is committed to improving digital accessibility for people with disabilities and providing an inclusive experience for website visitors.

We aim to identify, prevent and remove accessibility barriers in our website, forms, documents, media and digital communications where reasonably possible.

Accessibility is an ongoing responsibility. Technologies, content, assistive tools and user needs continue to change, so the website requires regular review and improvement.

02

Scope of this statement

This statement applies to:

  • The public website at tusics.org.
  • Public pages and navigation controlled by TUSIC.
  • Online forms embedded directly in TUSIC’s website.
  • Public PDF and downloadable documents published by TUSIC.
  • Images, videos and audio published directly by TUSIC.

It does not guarantee the accessibility of third-party websites, social-media platforms or external services that TUSIC does not control.

03

Accessibility standard and conformance target

TUSIC’s target is the Web Content Accessibility Guidelines 2.2 Level AA .

WCAG is organized around four broad principles: digital content should be perceivable, operable, understandable and robust.

01

Perceivable

Information should be available in ways users can perceive, including appropriate text alternatives.

02

Operable

Navigation and controls should work with a keyboard and other input methods.

03

Understandable

Content and interactions should be reasonably clear, consistent and predictable.

04

Robust

Content should work reliably with current browsers and assistive technologies.

No unsupported conformance claim

Identifying WCAG 2.2 AA as a target does not mean that every current page or third-party component has been verified as fully conformant.

04

Accessibility features we aim to provide

The website should support:

  • A visible “Skip to content” link.
  • Logical heading structure and page landmarks.
  • Keyboard access to navigation, controls and forms.
  • Visible keyboard focus indicators.
  • Sufficient text and interface colour contrast.
  • Alternative text for meaningful images.
  • Text labels or accessible names for form controls.
  • Clear instructions and identifiable form errors.
  • Responsive layouts that support zoom and text resizing.
  • Reduced-motion preferences where animation is used.
  • Descriptive link text rather than ambiguous wording.
  • Captions or transcripts for relevant media.
  • Tables with appropriate headings and structure.

These features must be tested on the production website; their inclusion in this statement is not proof that every page currently implements them correctly.

05

Accessible content practices

When creating or updating content, TUSIC should aim to:

  • Use plain, direct language where possible.
  • Break long information into descriptive sections.
  • Use real lists instead of manually typed symbols.
  • Avoid communicating meaning through colour alone.
  • Provide meaningful alternative text for relevant images.
  • Mark decorative images so assistive technology can ignore them.
  • Use descriptive titles for pages, documents and links.
  • Avoid unnecessary flashing, motion or autoplay.
  • Provide accessible alternatives for infographics.
  • Review uploaded documents before publication.

06

Technical compatibility

The website is intended to work with current versions of commonly used browsers and assistive technologies. These may include:

  • Keyboard-only navigation.
  • Screen readers.
  • Browser zoom and text resizing.
  • Voice input or speech-recognition software.
  • Screen magnification and high-contrast settings.
  • Reduced-motion preferences.
Testing details to complete

List the operating systems, browsers, screen readers, mobile devices and other assistive technologies used during TUSIC’s completed accessibility evaluation.

07

Known limitations

TUSIC should publish verified accessibility limitations after testing. Potential areas requiring particular attention include:

Bit Form contact forms

Form labels, error identification, keyboard operation, focus order and success messages require production testing.

Status: [NOT YET TESTED / RESULT]

PDF and downloadable documents

Older or third-party documents may lack tags, reading order, headings or text alternatives.

Status: [AUDIT REQUIRED]

Embedded third-party content

Video, maps, social-media content or external widgets may have limitations outside TUSIC’s control.

Status: [IDENTIFY ACTIVE EMBEDS]

Media captions and transcripts

Audio and video content requires review for accurate captions, transcripts and audio description needs.

Status: [MEDIA AUDIT REQUIRED]
Replace provisional limitations

After testing, list each confirmed barrier, affected content, planned remediation and expected completion date. Do not claim “no known issues” without evidence.

08

Third-party content and services

Some features may be supplied by third parties, including WordPress plugins, Bit Form, payment services, embedded media or social platforms.

TUSIC should consider accessibility when selecting and configuring providers, but may not be able to correct every barrier within an external system.

If a third-party feature is inaccessible, contact TUSIC and request the information or service through an alternative method.

09

Alternative formats and communication support

If you cannot access information or complete an action, you may request a reasonable alternative format or method.

Depending on the information and available resources, alternatives may include:

  • Accessible HTML instead of an inaccessible document.
  • A plain-text or large-print version.
  • A transcript for audio or video content.
  • Assistance completing an online form.
  • Information provided through another communication method.

TUSIC may need clarification about the barrier and the format that would be useful. Availability and delivery time will depend on the nature, complexity and urgency of the request.

10

Accessibility feedback process

Feedback from people with disabilities is important to identifying and addressing barriers.

When reporting a barrier, please include where possible:

  • The page address or name of the affected document.
  • The task you were trying to complete.
  • A description of the barrier.
  • Your browser, device or assistive technology, if relevant.
  • The alternative format or support that may help.
  • A safe way to contact you if you want a response.

Do not submit passwords, payment credentials or unrelated sensitive information.

11

Testing and continuous improvement

Accessibility evaluation should combine automated tools with manual testing because automated checks cannot identify every barrier.

A suitable review should include:

  • Keyboard-only navigation.
  • Focus order, visibility and focus trapping.
  • Screen-reader navigation and accessible names.
  • Heading, landmark and page-title structure.
  • Form labels, instructions, errors and confirmations.
  • Colour contrast and non-colour communication.
  • Zoom, text spacing and responsive reflow.
  • Images, icons, tables and embedded media.
  • Reduced motion and animation behaviour.
  • PDF and downloadable-document accessibility.
Evaluation record to complete

Evaluation method: [METHOD]
Evaluation date: [DATE]
Evaluator: [INTERNAL TEAM OR INDEPENDENT REVIEWER]
Pages and components tested: [SCOPE]
Conformance result: [VERIFIED RESULT]

12

Escalating an unresolved accessibility concern

If you believe your accessibility feedback has not been handled appropriately, ask for the matter to be reviewed through TUSIC’s complaints and feedback process.

Depending on TUSIC’s legal status and jurisdiction, you may also have rights through an applicable accessibility or human-rights authority. TUSIC must confirm which regimes apply before listing a specific regulator.

13

Contact us about accessibility

To report a barrier or request an alternative format, contact:

[FULL LEGAL NAME OF TUSIC ENTITY] Attention: [ACCESSIBILITY CONTACT OR RESPONSIBLE ROLE] Email: [ACCESSIBILITY OR GENERAL EMAIL ADDRESS] Telephone: [NUMBER, IF ACCESSIBLE PHONE SUPPORT EXISTS] Postal address: [COMPLETE POSTAL ADDRESS] Country: [COUNTRY]

You may also use the TUSIC contact form and select Accessibility request.

If the contact form itself is inaccessible, use the email address or another published contact method above.