All Portuguese Parish Councils (Juntas de Freguesia) are legally required to meet two essential digital requirements: accessibility (Decree-Law 83/2018, WCAG 2.1 AA) and data protection (GDPR + Law 58/2019). This guide is the complete legal checklist — what the law requires, what must be on the site, and how to implement.
Complete legal checklist for Portuguese Parish Council websites: WCAG 2.1 AA (DL 83/2018), GDPR, cookies, DPO and accessibility statement.
Table of Contents(17 sections)
- Decree-Law 83/2018 — WCAG 2.1 AA Accessibility
- Accessibility Statement — Mandatory Template
- GDPR + Law 58/2019 — Data Protection
- Complete Legal Checklist
- FAQ
- Real Modernization Cases in Portugal
- Detailed Funding: PRR Digital Capacity
- How to Apply for Funding
- Digital Governance Best Practices
- Key Metrics to Evaluate Progress
- WCAG 2.1 AA Technical Compliance Checklist for Portuguese Parish Councils
- RGPD Compliance Specifics for Portuguese Parish Councils
- Accessibility Statement Requirements
- Testing Tools and Methodology
- Common Non-Compliance Issues in Portuguese Public Sites
- Costs and Compliance Timeline
- FAQ: Accessibility and RGPD for Parish Councils
Decree-Law 83/2018 — WCAG 2.1 AA Accessibility
DL 83/2018 transposes European Directive 2016/2102 on accessibility of public sector websites and mobile applications. Applies to all public entities in Portugal: central government, municipalities, parish councils, hospitals, universities, public enterprises.
What the Law Requires
- WCAG 2.1 Level AA (or latest version, currently WCAG 2.2)
- Accessibility Statement published on the site, annually updated
- Contact mechanism for citizens to report accessibility problems
- Appeal procedure for unsatisfactory responses
- Monitoring by AMA (Portuguese Agency for Administrative Modernization)
Essential WCAG 2.1 AA Criteria
Perception
- Alt text on all images
- Captions on videos
- Color contrast ≥ 4.5:1 (normal text), ≥ 3:1 (large text)
- 200% text resize without loss of functionality
Operability
- Complete keyboard navigation
- No keyboard traps
- Sufficient time for tasks (no short timeouts)
- Descriptive link text (not “click here”)
Understandability
- Page language declared in HTML (lang=”pt-PT”)
- Clear simple language (B1/B2 level)
- Error identification in forms
- Clear instructions in all forms
Robustness
- Valid semantic HTML
- Screen reader compatibility
- ARIA labels on dynamic components
- Coherent heading structure
How to Test Site Accessibility
- AccessMonitor — AMA official tool
- WAVE — visual problem scanner
- Lighthouse (Chrome DevTools) — automatic accessibility audit
- NVDA/VoiceOver test — real screen readers, mandatory before launch
- Mouse-free navigation — try using site with keyboard only
Accessibility Statement — Mandatory Template
The statement must follow AMA format and include at least:
- Entity name and site URL
- Compliance level (fully, partially, or non-compliant)
- List of compliant sections/features
- List of identified problems and resolution timeline
- Contacts for accessibility problem reports
- Date of last review
GDPR + Law 58/2019 — Data Protection
GDPR (EU 2016/679) and national Law 58/2019 require any entity (including Parish Councils) processing personal data to implement specific measures.
Essential Obligations
- Privacy Policy clear and accessible on all pages
- Cookie banner compliant with ePrivacy — consent BEFORE loading third-party scripts
- Data Protection Officer (DPO) designated (mandatory for public entities)
- Legal basis for each processing (consent, legal obligation, public task)
- Data subject rights implemented: access, rectification, erasure, objection, portability
- Records of processing activities (Article 30 GDPR)
- Data breach notification to CNPD within 72h
- Impact assessment (DPIA) for high-risk processing
Privacy Policy — Minimum Elements
- Identity and contacts of controller (Parish Council)
- DPO contacts
- Purposes and legal basis for each processing
- Data collected and retention time
- Recipients (third-party sharing?)
- Data subject rights and how to exercise them
- Right to lodge complaint with CNPD
- International transfers (if applicable)
Cookie Banner — What Law Requires
Per ePrivacy Directive and 2022 CNPD guidelines, the banner must:
- Load BEFORE any non-essential cookies
- Offer equal ease of “Accept” and “Reject”
- No pre-selected options (opt-in mandatory)
- Allow granular configuration by category
- Securely store consent (or rejection)
- Allow revoking consent at any time
Strategic SEO Consulting
Custom strategy with real roadmap. From diagnostic to execution, we lead the entire SEO process for your business.
Complete Legal Checklist
- ✅ Accessibility Statement published (AMA format)
- ✅ Privacy Policy accessible on all pages
- ✅ Specific Cookie Policy
- ✅ Site terms of use
- ✅ Cookie banner compliant with CNPD
- ✅ DPO designated and contacts published
- ✅ Records of processing activities (internal)
- ✅ Forms with legal basis + explicit consent
- ✅ HTTPS on all pages
- ✅ Access logs with defined rotation
- ✅ Encrypted backups
- ✅ Accessibility problem reporting mechanism
- ✅ Documented WCAG 2.1 AA tests
Need a professional website for your parish council compliant with Portuguese law? See our Parish Council Websites service starting at €450+VAT. For municipalities, check our dedicated municipal council service. For independent WCAG 2.1 AA accessibility audits, see the specialized audit service.
FAQ
Can the Parish Council share DPO with the Municipality?
Yes. Possible and economically advisable. Many municipalities offer DPO service to their parishes. DPO can be internal or external contracted.
Is DPIA (Impact Assessment) mandatory?
Only for high-risk processing. For most typical Parish services, not mandatory but good practice.
What are GDPR fines for non-compliance?
For Portuguese public entities, Law 58/2019 limits fines: up to €500,000 for very serious violations, €1,000-€100,000 for less serious. Repeat offenses aggravate.
Must “Reject All” button have equal prominence?
Yes. CNPD was explicit in 2022 guidelines: “Accept” and “Reject” buttons must have same size, color, and visual prominence. “Dark patterns” (hidden reject buttons) are illegal.
How to backup GDPR-compliant?
Backups must be encrypted (AES-256+), stored offsite, with defined retention policy. Must include tested restore plan quarterly.
Real Modernization Cases in Portugal
Cascais Municipality
cm-cascais.pt portal completely redesigned 2024-2025 with focus on online services and citizen participation. 180% increase in online certificate requests vs counter in 12 months. Investment ~€250,000, 70% funded by PRR.
Guimarães Municipality
Municipal portal with real-time smart city dashboard (traffic, air quality, consumption). Recognized as European smart municipality reference case. Investment ~€400,000.
ANAFRE Associated Parishes
Collective program to digitize 500+ parishes with shared platform. Average cost per parish: €3,000 vs €15,000 if shouldloped individually.
Detailed Funding: PRR Digital Capacity
PRR has specific line for Public Administration:
- Total amount: €200M for AP digital transformation
- Co-financing rate: 60-85%
- Application deadline: end of 2026
- Eligible areas: digital portal, online services, interoperability, cybersecurity, cloud, open data
- Beneficiaries: Municipalities, Parish Councils, Metropolitan Areas
How to Apply for Funding
- Internal diagnosis — identify digital gaps and priority services
- Transformation plan — 24-36 month roadmap with measurable KPIs
- Detailed budget — breakdown by component
- Supplier consultation — 3 comparative proposals for expenses >€10,000
- Submission via Portal PT2030 or PRR
- Response in 60-90 days
- Implementation with quarterly milestones
Digital Governance Best Practices
- Internal DPO OR shared with Municipality: 70% compliance cost reduction
- IT Master Plan: coordinates all IT decisions
- Open-source first: prefer open solutions when equivalent to proprietary
- Hybrid cloud: sensitive data on national infrastructure, common services on public cloud
- Continuous training: 20h/year per employee in digital skills
- Strategic procurement: modular contracts, avoid vendor lock-in
Key Metrics to Evaluate Progress
- Service digitization rate (target: 70%+ by 2027)
- Digital usage rate: online vs counter
- Average response time per service
- Citizen NPS: quarterly satisfaction survey
- Published open datasets
- Cybersecurity incidents: zero data breaches goal
- Complaint rate reduction YoY
WCAG 2.1 AA Technical Compliance Checklist for Portuguese Parish Councils
Portuguese Decree-Law 83/2018 enforces EU Directive 2016/2102 on public sector accessibility. For parish councils (Juntas de Freguesia), compliance is not optional — it carries potential fines and reputational risk. Here is the technical checklist your website must meet.
Perceivable (Principle 1)
- Text alternatives (1.1.1): every image, chart, or non-text content needs meaningful alt text in Portuguese. Decorative images get empty alt=””. Logos get “Logótipo [Nome da Freguesia]”.
- Audio/video captions (1.2.2): all pre-recorded videos (assembly recordings, event videos) need Portuguese captions. YouTube auto-captions do not meet AA — mannual review required.
- Audio descriptions (1.2.5): videos with significant visual information need audio descriptions.
- Color contrast (1.4.3): text must have 4.5:1 contrast ratio against background (3:1 for large text 18pt+). Common failures: light gray text on white, blue links on dark backgrounds.
- Resize text (1.4.4): users must be able to zoom to 200% without horizontal scrolling or content loss.
- Images of text (1.4.5): use real text, not images containing text. Exception: logos.
- Reflow (1.4.10): content must work at 320px width without horizontal scrolling.
- Non-text contrast (1.4.11): UI components (buttons, form fields) need 3:1 contrast against adjacent colors.
Operable (Principle 2)
- Keyboard accessible (2.1.1): every function must work with keyboard alone. Test by unplugging mouse and navigating entire site using Tab, Shift+Tab, Enter, Space, arrow keys.
- No keyboard trap (2.1.2): keyboard focus must never get stuck. Modal dialogs need escape mechanism.
- Timing adjustable (2.2.1): if session timeouts exist, warn users and provide extension option.
- Three flashes threshold (2.3.1): no content flashing more than 3 times per second (seizure risk).
- Skip links (2.4.1): “Pular para o conteúdo principal” link at page top, visible on focus.
- Page titles (2.4.2): unique, descriptive titles for every page. Pattern: “Page — Freguesia de [Nome]”.
- Focus order (2.4.3): keyboard focus moves logically (top-to-bottom, left-to-right typically).
- Link purpose (2.4.4): link text must make sense out of context. Avoid “clique aqui” or “saber mais” alone.
- Multiple ways (2.4.5): at least 2 ways to find pages (menu + search, menu + sitemap).
- Headings and labels (2.4.6): descriptive, hierarchical. H1 for page title, H2 for sections, H3 for subsections.
- Focus visible (2.4.7): keyboard focus indicator always visible (don’t remove outline without replacement).
- Pointer gestures (2.5.1): no essential functionality requires complex gestures (pinch, swipe) without alternative.
- Pointer cancellation (2.5.2): actions trigger on up-event, not down-event (allows users to abort).
- Label in name (2.5.3): accessible name must contain visible label text (critical for voice control).
- Target size (2.5.5 AAA, recommended): clickable targets at least 44×44 CSS pixels.
Understandable (Principle 3)
- Language of page (3.1.1): HTML tag must have lang=”pt-PT” (Portuguese).
- Language of parts (3.1.2): content in different language needs lang attribute (e.g., English tourism info).
- On focus (3.2.1): focus does not trigger unexpected changes (no auto-navigation on focus).
- On input (3.2.2): changing a form field does not auto-submit without warning.
- Consistent navigation (3.2.3): navigation menu identical across all pages.
- Consistent identification (3.2.4): same components have same labels site-wide.
- Error identification (3.3.1): form errors described in text, not just color.
- Labels or instructions (3.3.2): form fields have visible labels (not just placeholders, which disappear on input).
- Error suggestion (3.3.3): when possible, suggest corrections for form errors.
- Error prevention (3.3.4): for legal/financial submissions (payment, bookings), allow review and correction before submission.
Robust (Principle 4)
- Parsing (4.1.1): HTML validates (W3C validator — no duplicate IDs, closed tags).
- Name, role, value (4.1.2): all UI components have accessible name and role (ARIA when needed).
- Status messages (4.1.3): dynamic updates announced to screen readers (ARIA live regions).
RGPD Compliance Specifics for Portuguese Parish Councils
Beyond accessibility, parish councils process personal data constantly: resident registrations, event signups, service requests. RGPD + Portuguese Law 58/2019 impose specific obligations.
Mandatory DPO Appointment
Every parish council must appoint a Data Protection Officer (DPO/Encarregado de Proteção de Dados):
- Appointment communicated to CNPD (Comissão National de Proteção de Dados)
- DPO contact details published on website (name, email, phone)
- DPO must be independent, with direct access to governing body
- Can be internal staff or external consultant (common for small freguesias to share DPO with association of municipalities)
Required Legal Pages
- Política de Privacidade (Privacy Policy): must detail every data processing activity
- Política de Cookies: list all cookies with purpose, retention, third parties
- Termos de Utilização: website terms of service
- Aviso Legal: parish council identification
- Reclamações e Direitos ARCO: how residents exercise RGPD rights
Cookie Compliance Specifics
- Pre-consent: only strictly necessary cookies load before consent
- Granular consent: user can accept/reject by category (functional, analytics, marketing)
- Reject button same prominence as Accept
- Preferences retrievable: user can change consent anytime
- Record of consent kept with timestamp and version of policy
Data Subject Rights Implementation
Website must provide clear mechanism for residents to exercise:
- Right of access (what data do you hold about me?)
- Right to rectification (correct inaccurate data)
- Right to erasure (delete my data where legally possible)
- Right to restriction (pause processing)
- Right to data portability (export my data in machine-readable format)
- Right to object (stop processing for specific purposes)
Response time: 1 month maximum, extendable by 2 months for complex requests.
Breach Notification Protocol
- Data breach must be reported to CNPD within 72 hours of detection
- If high risk to residents, affected individuals must also be notified
- Breach register must be maintained (even if not reported)
- Response plan documented in advance (who does what, how, when)
Accessibility Statement Requirements
Portuguese law requires every public sector website to publish an Accessibility Statement:
- Updated annually or when major changes occur
- Published at predictable URL (/declaracao-acessibilidade/ or /acessibilidade/)
- Linked from footer of every page
- Must detail: compliance level (fully/partially/non-compliant), non-conformities, alternatives, feedback mechanism
- Must include contact for inaccessible content requests
- Published both in HTML and PDF format
Testing Tools and Methodology
Automated Testing (Catches 30-40%)
- WAVE (wave.webaim.org): browser extension, visual overlay of issues
- axe DevTools: comprehensive rule-based testing, shouldloper-friendly
- Lighthouse Accessibility: built into Chrome DevTools, scores 0-100
- Siteimprove (free trial): comprehensive multi-page scanning
- Pa11y: command-line, integratable into CI/CD
Mannual Testing (Catches 60-70%)
- Keyboard-only navigation (unplug mouse, test every function)
- Screen reader testing: NVDA (free Windows), VoiceOver (free macOS), Jlarge clouds internacionais (commercial)
- 200% zoom test
- Mobile responsive at 320px
- Color contrast with Contrast Analyzer
- Images-off test (do pages still make sense?)
User Testing (Catches Remaining Issues)
- Test with 3-5 real users with disabilities
- Local associations like ACAPO (visually impaired), APD (physical disabilities) can facilitate
- Document findings, prioritize fixes, retest
Common Non-Compliance Issues in Portuguese Public Sites
- Scanned PDFs: images of text, not real text. Must OCR and tag properly.
- Image-based navigation: menu items as images without alt text
- Missing form labels: contact forms using only placeholder text
- Low contrast: stylish light-gray on white designs failing 4.5:1
- Keyboard traps in modals: popups that don’t release focus on Escape
- Missing lang attribute: HTML tag without lang=”pt-PT”
- Non-descriptive link text: “clique aqui” everywhere
- Broken skip links: implemented but not functional
- Flash/motion without controls: auto-playing carousels
- Inaccessible calendars: event calendars using divs instead of semantic markup
Costs and Compliance Timeline
For New Websites
Building accessibly from the start adds 10-20% to shouldlopment cost. For a parish council website at €2,500 base, expect €2,750-3,000 total for accessible version. We include this at no extra cost in our 450€+VAT parish council website service.
For Existing Websites (Remediation)
- Minor fixes (contrast, alt text, labels): €300-800
- Medium fixes (navigation, forms, PDFs): €800-2,500
- Major rebuild for compliance: €2,000-5,000 (often cheaper to rebuild than patch)
FAQ: Accessibility and RGPD for Parish Councils
What are the fines for non-compliance?
Accessibility: no direct fines yet but court orders possible. RGPD: up to 20M€ or 4% of revenue — for public bodies, Law 58/2019 reduces these but still substantial.
Do we need to make old PDFs accessible?
Yes, but prioritization is allowed. Current documents must be accessible. Older archived documents can have accessibility statement explaining alternative access.
Can we use third-party embeds (Facebook, Google Maps)?
Yes, but you’re responsible for ensuring they don’t block cookie consent, provide alternative text content, and are keyboard accessible.
How often should we audit?
Formal audit annually. Automated scanning monthly. Mannual spot-checks on new content weekly.