State University
High student numbers, multiple faculty sites, legacy OBS infrastructure. Budget constraints are significant.
- Multi-faculty domain support
- YÖK Disability Unit integration kit
- OBS vendor violation report
Bring your OBS, course registration, library portal and e-learning systems up to WCAG 2.2 A level. Achieve compliance before the 21 June 2026 deadline; protect your students with disabilities in their right to education.
All state and foundation universities in Turkey fall within the scope of Circular 2025/10. State universities, as public institutions, and foundation universities, as institutions serving students, are in the 1-year compliance period group.
For each non-compliance identified after 21 June 2026, an administrative fine of 5.000–25.000 TL (annual cap 500.000 TL) may apply. In addition, the YÖK Disabled Student Unit directive safeguards access to digital environments for students with disabilities; for foundation universities, reputational and student-preference risk is also high.
State universities, foundation universities and colleges have different priorities.
High student numbers, multiple faculty sites, legacy OBS infrastructure. Budget constraints are significant.
Brand reputation is critical, modern web infrastructure. Targeting international students, multilingual content.
Simplified structure, a single site and announcement system. Fast compliance, low technical complexity.
The most common WCAG 2.2 A non-compliances in Turkey's university systems.
Grade viewing, transcript, exam schedule and course calendar screens usually run inside an iframe. Keyboard navigability, form labels, error messages and screen reader compatibility are missing. Visually impaired students cannot access grade information independently.
Course selection interfaces and LMS (Moodle, ALMS, Microsoft Teams Education) integrations are mostly inaccessible. AJAX resource updates are not announced to the screen reader; in video lectures, captions and audio description are missing (WCAG 1.2.2, 1.2.5).
Scanned PDFs uploaded by academics cannot be processed by screen readers. Online library databases (Ulakbim, ProQuest, etc.) cannot be controlled when embedded inside an iframe. WCAG 1.3.1 and 4.1.2 violations are common.
For all your academic web assets, from the rectorate homepage to the OBS login screen.
Multi-page scanning for the homepage, sub-pages and faculty sites. For each unit, a violation list prioritized as Critical / Serious / Moderate / Minor is generated as a PDF.
The Shadow DOM widget works without breaking the CSS/JS structure of the OBS / LMS interface. Visually impaired, hearing impaired, dyslexia and cognitive impairment profiles make access easier for students.
The Disabled Student Unit contact details are included automatically. The statement is added to the footer; a feedback channel is opened for students. A brand-focused template is also available for foundation universities.
The Shadow DOM architecture does not break the CSS/JS structure of the OBS/LMS interface.
Tested integrations. For custom OBS systems you can technical feasibility request.
The risk for a university is not limited to fines. YÖK audits, students' rights with disabilities and brand reputation must also be considered.
Overlay tools inject a single script and make big promises. This approach does not solve most WCAG violations and creates legal risk. We chose a different path.
One line of script, a big promise.
"We added a button, the site became accessible" is not how it actually works.
Assistive widget, real scanner, documentation.
Says it plainly: full compliance requires source code fixes and manual review. We shorten the path and produce the evidence.
A practical 5-step plan for the IT Department.
Enter the rectorate homepage URL to receive your first WCAG 2.2 A violation list as a PDF. On Pro/Business plans, multi-page scanning for academic unit sites is unlocked.
A single line of script tag is added to the main site and academic unit sub-sites. On the OBS login screen, students with disabilities gain access to a screen reader, dyslexia mode, contrast and similar tools.
Critical violations in the OBS, course registration and LMS interfaces are closed first. For vendor products, a compliance requirement list is shared with the supplier.
A statement signed by the rectorate and the Disabled Student Unit is added to the footer. The Disabled Student Unit email address is published for student feedback.
Once the WCAG A criteria are met, a logo application is made to the Ministry of Family and Social Services; YÖK is informed in the annual accessibility report.
cerez.io the differences between foreign solutions and manual compliance.
OneTrust / UserWay / AccessiBe
In-house team and consultants
Turkey-based local SaaS, cerez.io
cerez.io is currently in the early access phase. The statements below are compiled from the technical feedback of universities in the pilot program.
We used the cerez.io violation report as a vendor brief with our OBS supplier. The output of the 19 static rules was added directly to the sprint backlog together with our development team.
The integration with the Disabled Student Unit and the statement generator are very practical. The 10-language widget became a reason to choose it for our Erasmus students.
* Statements have been anonymized as part of the pilot program.
Pro is recommended for foundation and small state universities; Enterprise for large universities and multiple campuses.
3 domains (main site and 2 sub-units), weekly scanning, statement generator, AI alt-text suggestions.
Unlimited domains (including faculty sites), SLA, dedicated support, white-label.
Find out the WCAG 2.2 A status of your rectorate homepage with a free scan. Act before 21 June 2026 draws near.