--- title: "Romanian Law Requires Public Institutions to Adopt Standardised Navigation Menus on Their Websites" date: 2026-05-23 description: "A practical and legislative guide to the mandatory structure of public institution websites in Romania: standardised navigation, web accessibility, GDPR, cybersecurity, and integrated government platforms." author: "Petru Cojocaru" categories: - name: "Website creation" url: "https://cojocarupetru.info/website-creation.md" --- # Romanian Law Requires Public Institutions to Adopt Standardised Navigation Menus on Their Websites Romanian legislation has established precise standards for structuring and organising information on the websites of public institutions. [![Romanian Law Requires Public Institutions to Adopt Standardised Navigation Menus on Their Websites](https://cojocarupetru.info/images/Realizare-site/meniuri-web-site4.jpg "Romanian Law Requires Public Institutions to Adopt Standardised Navigation Menus on Their Websites")](https://cojocarupetru.info/index.php?option=com_content&view=article&id=360:standardised-navigation-menus&catid=26:website-creation&lang=en-GB&Itemid=510)The stated aim is accessibility and transparency in the relationship between citizens and the administration — with particular emphasis on the sites of local councils and educational establishments. This article does not set out to be an investigation in the journalistic sense of the word: all the reference documents are publicly available to anyone on [legislatie.just.ro](https://legislatie.just.ro). What it offers instead is a systematic reading of those documents — one that will prove useful to anyone who builds, audits, or maintains a public institution's website. In the context of the digitalisation of public administration and growing demands for transparency, Romanian legislation ([Government Decision 830/2022](https://legislatie.just.ro/Public/DetaliiDocument/256836)) has established standards for the structuring and organisation of information on public institution websites. This detailed regulation is aimed at ensuring a high degree of accessibility and transparency in the relationship between citizens and public administration — with particular relevance to the creation of school websites and local council websites. **Listen to the audio summary in Romanian and English** --- **What follows** is a mapping of the system by which Romania has transformed the relationship between citizens and public institutions through the regulation of how authorities present their information online. The documents examined reveal a profound shift in the very concept of administrative transparency. --- ## The Basic Legislative Framework ### Law No. 544/2001 — Access to Public Information [Law No. 544/2001](https://legislatie.just.ro/Public/DetaliiDocumentAfis/34200) on free access to information of public interest forms the legal bedrock of the entire system. Under this law, **information of public interest** means any information that concerns the activities of a public authority or arises from those activities, regardless of medium, form, or means of expression. The definition is deliberately broad, and it creates extensive obligations for all public institutions. ### Government Decision No. 478/2016 — The Mandatory Site Structure [Government Decision No. 478/2016](https://legislatie.just.ro/Public/DetaliiDocument/178281), which amended and supplemented the Methodological Rules for implementing Law No. 544/2001, introduced the mandatory navigation structure. Its adoption followed an assessment by the Ministry for Public Consultation and Civic Dialogue (MCPDC), which found worrying levels of compliance: | Institution Type | Average Compliance (2016) | | --- | --- | | Ministries | 62% | | Prefecture Institutions | 66% | | County Councils | 72% | | Municipal Councils | 58% | These figures can be read in two ways: as the failure of an unregulated system, or as a reasonable starting point for an administrative apparatus in the process of digitalisation. Whichever interpretation one favours, they provided the justification for standardisation through law. ### Government Decision No. 830/2022 — Updated Standards [G.D. 830/2022](https://legislatie.just.ro/Public/DetaliiDocument/256836) consolidated and updated the existing requirements, extending existing obligations and aligning them with technological and European legislative developments in the period 2016–2022. --- ## The Mandatory Structure: Five Sections The law prescribes the organisation of content into **five principal sections**, each with precise sub-sections. ### Section I — About the Institution **a) Legislation** - All legislative acts governing the organisation and functioning of the institution - Direct links to [legislatie.just.ro](http://legislatie.just.ro) - Mandatory format: PDF **b) Leadership** - A complete list of persons holding leadership positions (full name required) - For senior officials (ministers, prefects, county council presidents, directors): CVs, official photographs, updated schedules - Mandatory link to [ruti.gov.ro](http://ruti.gov.ro) for the leadership's agenda **c) Organisation** - The organisational and functional regulations - A complete organisational chart, including the names of persons in leadership positions - The number of posts in each structural unit (subject to compliance with legislation on classified information) **d) Subordinate Institutions** - A complete list, with contact details, of all subordinate, coordinated, or supervised institutions --- ### Section II — Information of Public Interest **a) Requesting Information** - A detailed procedure for submitting information requests - Standard forms, with estimated completion time - Contact details of the officer responsible for implementing Law 544/2001 **b) Proactive Disclosure** - A list of categories of documents produced and/or managed by the institution - Documents communicated automatically, without any formal request **c) Programmes and Strategies** - Accepted formats: .pdf, intelligent PDF, .doc, .docx, .odt **d) Reports and Studies** - Annual activity report - Annual vocational training report - Annual audit reports - Progress reports on national strategies - Ethics adviser's reports - Studies produced using the institution's own resources, through subcontracting, or from external sources --- ### Section III — Financial Activity **a) Budget Transparency** — mandatory format: .ods, .xml, .xls or .xlsx - The revenue and expenditure budget - Statement of payments made - Statement of salary entitlements **b) Public Procurement** - Procurement plan and investment plan - Consolidated register of procurement contracts - Contracts with a value exceeding €5,000 (from 2015 onwards) --- ### Section IV — Asset and Interest Declarations Asset and interest declarations in accordance with the relevant legal annex, with mandatory updating and unrestricted public access. --- ### Section V — Standard Forms - Forms for requests under Law No. 544/2001 - Forms for contesting decisions - Estimated completion time indicated for each form - Accepted formats: .pdf, intelligent PDF, .doc, .docx, .odt --- ## Web Accessibility — Obligations Regarding Persons with Disabilities One aspect frequently overlooked in discussions of institutional websites is **accessibility for persons with disabilities**. [Law No. 448/2006](https://legislatie.just.ro/Public/DetaliiDocumentAfis/75448) on the protection and promotion of the rights of persons with disabilities, read together with EU Directive 2016/2102, obliges public institutions to comply with the **WCAG 2.1 standard at the minimum level of AA**. ### What WCAG 2.1 AA Means in Practice - Alternative text (`alt`) for all images carrying informational content - A minimum contrast ratio of 4.5:1 between text and background - Full keyboard navigation, without dependence on a mouse - Subtitles for audio and video content - Accessible PDF documents (with a heading structure and selectable text) ### Recommended Verification Tools | Tool | Use | Access | | --- | --- | --- | | [WAVE](https://wave.webaim.org) | Visual accessibility audit | Free, online | | [axe DevTools](https://www.deque.com/axe/) | Browser extension, detailed audit | Free (basic) | | Google Lighthouse | Audit integrated in Chrome DevTools | Free, included in browser | Institutions that fail to meet accessibility requirements may be reported to the Authority for the Digitalisation of Romania (ADR). --- ## GDPR and Data Protection on Public Websites [Regulation (EU) 2016/679](https://eur-lex.europa.eu/legal-content/RO/TXT/?uri=CELEX%3A32016R0679) (GDPR), transposed into Romanian law through [Law No. 190/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/201676) and [Law No. 129/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/200435), imposes concrete obligations on any website that collects or processes personal data. ### What Must Not Be Published on a Public Website A few examples of data that **must not appear** on a public institution's website, even if it exists within internal documents: - Pupils' personal data (national ID numbers, addresses, medical information) on school websites - Employees' data beyond what is strictly necessary for transparency purposes (job title, duties) - Images of individuals captured by surveillance cameras - Petitioners' home addresses in published documents ### Minimum GDPR Technical Obligations for Websites - **Privacy Policy** — a dedicated page, accessible from any page on the site, explaining what data is collected, for what purpose, and for how long it is retained - **Cookie Policy** — a consent banner on the first visit; non-essential cookies activated only after the user's explicit consent - **Contact Form** — a checkbox with a link to the privacy policy, not pre-ticked by default - **DPO Contact Details** — the Data Protection Officer (or the institution's contact details for GDPR requests) must be prominently published Breaches of GDPR may be reported to the [National Supervisory Authority for Personal Data Processing (ANSPDCP)](https://www.dataprotection.ro). --- ## Cybersecurity — Minimum Technical Requirements The digital presence of a public institution also entails cybersecurity responsibilities, regulated by [Law No. 362/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/203530) on the security of networks and information systems (transposing the NIS Directive). ### Essential Technical Requirements **HTTPS is Mandatory.** Every public institution website must operate exclusively over HTTPS. A valid SSL/TLS certificate is now free (Let's Encrypt) and therefore provides no grounds for a cost-based excuse for its absence. Modern browsers flag HTTP sites as insecure, which directly undermines the institution's credibility. **CMS Security Updates.** Regardless of the platform in use — WordPress, Joomla, Drupal, or a government-specific solution — software versions must be kept current. Unpatched vulnerabilities are the primary cause of institutional website compromises in Romania. **Regular Backups.** Automated backups (weekly at a minimum, daily where possible) stored off the primary server are a basic requirement for service continuity. **Choosing a CMS Platform** | Platform | Advantages for Public Institutions | Notes | | --- | --- | --- | | WordPress | Large ecosystem, easy to manage | Requires security plugins (Wordfence, iThemes) and frequent updates | | Joomla | Granular access control, well-suited to complex structures | Less vulnerable through obscurity, but more limited documentation | | Drupal | Robust for large institutions, high native security | Steep learning curve | | Government Solutions | Native compliance with Romanian requirements | Availability and support variable | --- ## Integrated Government Platforms (2025–2026) The digital infrastructure of Romanian public administration has expanded significantly in recent years through specialist platforms with which institutional websites must or may integrate. **[e-consultare.gov.ro](https://e-consultare.gov.ro)** — The national public consultation platform. Public institutions launching draft legislation or strategies are obliged to publish them on this platform as well as on their own site. The link to any active consultation ought also to be reflected in the "Programmes and Strategies" section of the institutional website. **[tablou.gov.ro — Info-Transparency](https://tablou.gov.ro)** — The national dashboard for monitoring institutional transparency. Data from individual institutions is aggregated and monitored centrally. A well-structured website contributes directly to the institution's transparency score within this system. **[ruti.gov.ro](http://ruti.gov.ro)** — The platform for senior officials' working agendas, to which the institutional website must link mandatorily from the "Leadership" section. **SIIP (Integrated Information System for Pre-University Education)** — For educational institutions, information published on the website must be consistent with the data held in SIIP. Discrepancies can create difficulties during inspection and accreditation processes. --- ## Penalties and Control Mechanisms The explicit or tacit refusal of the designated employee to apply the provisions of Law 544/2001 constitutes a disciplinary offence. MCPDC assessments are conducted monthly at the level of both central and local executive bodies, with findings consolidated nationally. **Who May Report Non-Compliance:** - Any citizen, through a written request addressed to the institution or directly to the administrative court - The Authority for the Digitalisation of Romania (ADR) — for web accessibility - ANSPDCP — for GDPR non-compliance - DNSC (National Directorate of Cyber Security) — for security incidents --- ## Practical Limitations and Challenges The legislative framework described above is complete on paper. The reality of implementation frequently tells a different story, and not always through bad faith. **Insufficient budgets.** A rural commune council often operates with a near-nonexistent IT budget. Full compliance requires either a dedicated in-house webmaster (a post frequently left unfilled) or an external contractor — a cost that local budgets do not always cover. **Staff without digital competencies.** The official designated as responsible for updating the website often lacks any technical training. Publishing a document in .xlsx format or updating an organisational chart can become a genuine obstacle without technical support. **Administrative overload.** The sheer volume of documents that must be published and continuously updated — reports, asset declarations, agendas, contracts — creates a relentless workload for institutions with limited staff. Automating these workflows through CMS integration or government APIs remains a solution applied only sporadically. **Real-time updating.** The law requires the periodic updating of agendas and documents without always defining precise intervals. This ambiguity permits loose interpretation and reduces the effectiveness of the monitoring mechanism. --- ## Frequently Asked Questions **What happens in practice if an institution fails to comply with the mandatory structure?** Citizens may submit information requests and, in the event of refusal, may take the matter to the administrative court. The responsible official faces disciplinary sanctions. In practice, direct administrative sanctions for the absence of a section from a website are rare; pressure comes primarily from citizens' complaints and MCPDC assessments. **Who actually verifies compliance?** The MCPDC conducts monthly assessments of central institutions. At the local level, oversight is more diffuse — it may arise from prefectural inspections, citizens' complaints, or court reviews. There is no authority dedicated exclusively to auditing institutional websites. **How can documents be updated automatically on a website?** Existing technical solutions include API integration with government platforms (e-consultare, SEAP for procurement), synchronisation plugins for popular CMSs, or automated publication scripts connected to internal document workflows. These are more common among larger institutions; smaller councils tend to work predominantly by hand. **Is there an official compliance checklist?** No official checklist published by a central authority exists. The MCPDC periodically publishes assessment methodologies, but not a downloadable checklist for institutional webmasters. This absence is itself a problem of the state's communication with local administrations. **Must the website be mobile-friendly?** The law does not explicitly mandate responsive design, but WCAG 2.1 AA accessibility standards include the requirement that a site be usable on devices with screens of different sizes. In practice, any modern CMS generates responsive sites by default. --- ## Conclusions Romanian legislation has built a coherent and detailed framework of digital transparency for public institutions. The mandatory site structure, accessibility requirements, GDPR obligations, and security standards together form a body of rules applicable to any council, school, or public institution in Romania. The difficulty does not lie in understanding the rules — they are clear. It lies in implementing them with limited human and financial resources, within a non-uniform administrative apparatus. This tension between the legal standard and the actual capacity to comply is the structural problem that no piece of legislation has yet resolved. --- ## Bibliography and Legislative Sources - [Law No. 544/2001](https://legislatie.just.ro/Public/DetaliiDocumentAfis/34200) — free access to public information - [G.D. No. 478/2016](https://legislatie.just.ro/Public/DetaliiDocument/178281) — mandatory site structure - [G.D. No. 830/2022](https://legislatie.just.ro/Public/DetaliiDocument/256836) — updated standards - [Regulation (EU) 2016/679](https://eur-lex.europa.eu/legal-content/RO/TXT/?uri=CELEX%3A32016R0679) — GDPR - [Law No. 190/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/201676) — GDPR transposition - [Law No. 129/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/200435) — GDPR amendments - [Law No. 448/2006](https://legislatie.just.ro/Public/DetaliiDocumentAfis/75448) — rights of persons with disabilities - [Law No. 362/2018](https://legislatie.just.ro/Public/DetaliiDocumentAfis/203530) — security of networks and information systems (NIS) - [ruti.gov.ro](http://ruti.gov.ro) — leadership agendas - [e-consultare.gov.ro](https://e-consultare.gov.ro) — public consultation --- ## Author's Note *On the limits of this article. Petru Cojocaru, May 2026* --- There is a kind of intellectual honesty that almost nobody practises in content marketing: saying, after you have written an article, what you have left unsaid and why. Not out of performative modesty. But because the reader who understands the limits of a text makes better use of it. This article has several layers of limitation. Some are technical. Others are methodological. A few are subjective, and however hard I tried, I could not entirely escape them. --- **1. The single-source limitation** The entire article rests on publicly available legislative documents. I did not interview a single public official who has actually implemented these requirements. I did not speak to a webmaster from a rural council managing a site built on Joomla 3.9 on twenty-euros-a-month hosting. I did not consult an MCPDC inspector who has conducted the monthly assessments the law describes. The direct consequence is this: the article describes what the law says must exist, not what actually exists. The distance between the two is not small. In some cases, it is abyssal. Any practitioner in this field — a council employee in a small village, an IT officer at a school inspectorate — knows things about that distance which no document can tell you. Those things are not in this article. --- **2. The limitation of declared and undeclared technical competence** The sections on cybersecurity and web accessibility are written with sufficient accuracy for a non-specialist reader. They are not written with sufficient depth for a specialist. When I recommend WAVE, axe and Lighthouse as WCAG verification tools, I do not note that these cover only around 30–40% of WCAG 2.1 AA criteria — the remainder requires manual testing or testing with users who have real disabilities. A serious accessibility audit cannot be done with a browser extension. It requires screen readers, blind users, users with limited mobility, and real navigation scenarios. That nuance is absent from the text. I chose immediate usefulness over complete technical precision. It was a conscious choice, but it must be owned. Likewise, the comparative table of WordPress, Joomla, and Drupal is a simplification that could mislead. The security of a CMS does not depend on the platform itself, but on its specific configuration, the hosting environment, the installed plugins, and the administrator's updating discipline. I presented a statistical average of risk as though it were an intrinsic property of the platform. It is not. --- **3. The geographical and dimensional limitation** The article treats all public institutions as a single homogeneous category. They are not. A ministry with five hundred employees and a dedicated IT department inhabits an entirely different digital reality from a council serving twelve hundred inhabitants, where a single employee is responsible for everything that falls under the heading of "computers". The law imposes identical obligations on both. The article describes them as though they were equally capable of meeting those obligations. This homogenisation is a problem of honesty towards the reader who runs a small institution and reads the article hoping to understand what is expected of them. What is expected is often impossible with the resources they have. The article does not tell them that clearly enough. The section "Practical Limitations and Challenges" touches on the problem. It does not resolve it. --- **4. The temporal limitation and the problem of updating** Legislation changes. Government platforms change. Links die. When I write that [ruti.gov.ro](http://ruti.gov.ro) is the mandatory platform for senior officials' agendas, I write something true as of the date of publication. I do not know whether it will still be true in two years' time. I do not know whether the platform will still be operational, whether it will have been replaced, or whether the obligation will have been modified by a new government decision. The article has no guaranteed update mechanism. It carries a `lastmod` date in the header, and that date depends on my own discipline of revision. That discipline is not guaranteed by any external system. A reader who finds the article through a search engine two years after publication has no immediate way of knowing what is current and what is already out of date. This is a structural problem with any web content of this kind, and I have no elegant solution for it. --- **5. The limitation of SEO as a distortion of intent** The article was written with its visibility in search engines partly in mind. This is not in itself a moral problem — I write for a web agency's website and I have legitimate commercial interests. The problem arises when the SEO intent distorts the editorial intent. In an earlier version of the article, the phrases "school website development" and "council website development" appeared seven times, sometimes with no organic connection to the sentence in which they were inserted. I reduced them and redistributed them. I did not remove them entirely, because doing so would have been commercially impractical. A tension remains unresolved: the article simultaneously serves the reader who wants to understand the legislation and the prospective client searching Google for "council website development". These two audiences have partly different needs. The text attempts to serve both and, inevitably, serves neither perfectly. --- **6. The limitation of government platforms presented as stable** The section on integrated government platforms — e-consultare, Info-Transparency, SIIP — presents these systems as though they were functional, stable, and continuously supported. The practical experience of working with Romanian public institutions suggests that this assumption is optimistic. Romanian government platforms have a documented history of discontinuity: URL changes, periods of downtime, migrations between systems without public communication, incorrect or out-of-date data. To present them as reliable integration solutions without that caveat is an omission likely to produce frustration at the implementation stage. --- **7. The limitation of the author's voice versus the institution's voice** The article is written in impersonal third person for the most part, with the exception of this note. That choice creates an illusion of neutrality which I cannot fully guarantee. I have concrete experience in building websites for Romanian public institutions. That experience inevitably colours what I choose to emphasise, what I consider important, what I pass over more quickly. A lawyer specialising in administrative law would have written this differently. A web accessibility specialist would have written it differently. A public official with ten years' experience would have written it differently. This article was written by someone who builds websites and who read the legislation carefully. That is its perspective, and its only one. --- **What remains valid in spite of all this** The structure of the five mandatory sections is rendered accurately. The technical format requirements are listed faithfully against the normative text. The accessibility and security tool recommendations serve as useful starting points. The FAQ addresses the questions I actually receive in practice. For anyone starting from scratch in building or auditing a Romanian public institution website, the article provides a workable map. It is not the complete map. No map ever is the territory. --- *These limitations do not nullify the article's usefulness. They contextualise it.* *P.C.* --- *Source: https://cojocarupetru.info/ | Auto-generated for AI indexing* --- --- # 20 Questions and Answers **Q1. What is the fundamental legal basis for the mandatory website structure of Romanian public institutions?** A. Law No. 544/2001 on free access to information of public interest provides the legal bedrock. Under this law, any information concerning or arising from the activities of a public authority constitutes public interest information, regardless of medium, form, or means of expression. --- **Q2. Which government decisions introduced and then updated the mandatory website structure?** A. Government Decision No. 478/2016 introduced the mandatory navigation menu structure, amending the Methodological Rules for Law 544/2001. Government Decision No. 830/2022 subsequently consolidated and updated the requirements, aligning them with technological and European legislative developments. --- **Q3. What did the 2016 MCPDC assessment reveal about compliance levels, and which institution type had the lowest score?** A. The assessment found that compliance averaged 62% for ministries, 66% for prefecture institutions, 72% for county councils, and 58% for municipal councils. Municipal councils had the lowest average compliance, at 58%. --- **Q4. How many principal sections must a public institution website contain, and what are they?** A. Five principal sections are mandated: (I) About the Institution; (II) Information of Public Interest; (III) Financial Activity; (IV) Asset and Interest Declarations; (V) Standard Forms. Each section has precisely defined sub-sections. --- **Q5. What specific information must the "Leadership" sub-section contain?** A. It must include the complete list of persons holding leadership positions, with full names. For senior officials — ministers, prefects, county council presidents, and directors — it must also include CVs, official photographs, and updated schedules, together with a mandatory link to the ruti.gov.ro platform for agendas. --- **Q6. Which web accessibility standard must Romanian public institution websites meet, and under which law?** A. They must meet the WCAG 2.1 standard at the minimum level of AA. This obligation derives from Law No. 448/2006 on the rights of persons with disabilities, read in conjunction with EU Directive 2016/2102. --- **Q7. What are the five key practical requirements of WCAG 2.1 AA as they apply to institutional websites?** A. The five requirements are: alternative text for all informational images; a minimum text-to-background contrast ratio of 4.5:1; full keyboard navigation without dependence on a mouse; subtitles for audio and video content; and accessible PDF documents with a heading structure and selectable text. --- **Q8. Which free tools can institutions use to test WCAG compliance, and what are their limitations?** A. WAVE, axe DevTools, and Google Lighthouse are the commonly recommended tools. However, as the author's note points out, these cover only approximately 30–40% of WCAG 2.1 AA criteria. The remainder requires manual testing or testing with real users with disabilities. --- **Q9. Under GDPR, what categories of data must NOT appear on a school's or council's public website?** A. Pupils' personal data (national ID numbers, addresses, medical information) must not appear on school websites. More broadly, employees' data beyond what is strictly necessary for transparency, images captured by surveillance cameras, and petitioners' home addresses in published documents must not be published publicly. --- **Q10. What are the four minimum GDPR technical obligations for a public institution website?** A. First, a dedicated privacy policy page, accessible from any page. Second, a cookie consent banner with non-essential cookies inactive until explicit consent is given. Third, a contact form with an un-pre-ticked privacy policy checkbox. Fourth, the prominent publication of the Data Protection Officer's contact details. --- **Q11. Is an SSL/TLS certificate legally required for public institution websites, and is cost a valid justification for its absence?** A. HTTPS is mandatory under Law No. 362/2018. Cost is not a valid justification: free certificates are available through Let's Encrypt. Modern browsers mark HTTP sites as insecure, directly damaging institutional credibility. --- **Q12. Among WordPress, Joomla, and Drupal, which CMS is described as best suited to complex institutional structures, and why?** A. Joomla is identified as particularly suited to complex structures, owing to its granular access control capabilities. The article notes, however, that the author's own caveat qualifies this: security ultimately depends not on the platform but on specific configuration, hosting, installed plugins, and updating discipline. --- **Q13. What is the e-consultare.gov.ro platform, and what obligation does it create for institutions launching new legislation or strategies?** A. It is the national public consultation platform. Institutions launching draft legislation or strategies are obliged to publish them on this platform in addition to their own website. The institutional site should also reflect a link to any active consultation in its "Programmes and Strategies" section. --- **Q14. What is the Info-Transparency dashboard (tablou.gov.ro), and how does a well-structured website contribute to it?** A. It is the national dashboard for monitoring institutional transparency, aggregating and centrally monitoring data from individual institutions. A well-structured website contributes directly to the institution's transparency score within this system. --- **Q15. What sanctions can an institution face for non-compliance with Law 544/2001, and how are they typically triggered in practice?** A. An official's explicit or tacit refusal to implement the law's provisions constitutes a disciplinary offence. Citizens may submit information requests and, in the event of refusal, take the matter to the administrative court. In practice, direct administrative sanctions for missing website sections are rare; pressure comes mainly from citizens' complaints and MCPDC assessments. --- **Q16. Which bodies are responsible for enforcing different aspects of institutional website compliance?** A. The MCPDC conducts monthly assessments of central institutions. The Authority for the Digitalisation of Romania (ADR) oversees web accessibility. The ANSPDCP handles GDPR complaints. The DNSC (National Directorate of Cyber Security) responds to security incidents. Prefectures and courts also play a role at the local level. --- **Q17. What are the three main technical approaches to automating document publishing on institutional websites?** A. The three approaches are: API integration with government platforms such as e-consultare and SEAP; synchronisation plugins for popular CMS platforms; and automated publication scripts connected to internal document workflows. These are most commonly deployed by larger institutions; smaller councils predominantly work by hand. --- **Q18. What structural problem does the author identify as one that no piece of legislation has yet resolved?** A. The tension between the legal standard and the actual capacity to comply. The law imposes identical obligations on a ministry with five hundred staff and a dedicated IT department and on a commune council with a single employee managing everything digital — and no legislation has addressed this fundamental disparity of resources. --- **Q19. Why does the article acknowledge a limitation concerning the mandatory government platforms such as ruti.gov.ro?** A. Romanian government platforms have a documented history of discontinuity — URL changes, periods of downtime, system migrations without public communication, and inaccurate data. Presenting them as reliable and stable integration solutions without this caveat risks producing frustration at the implementation stage. --- **Q20. Does the law explicitly require responsive (mobile-friendly) design for public institution websites?** A. The law does not explicitly mandate responsive design. However, WCAG 2.1 AA accessibility standards require that a site be usable on devices with screens of varying sizes. In practice, any modern CMS generates responsive sites as a default.