Research · Analysis of the bill

Analysis of bill PL-x 300/2026

This is my analysis of bill PL-x 300/2026 on the standardisation of digital design and on ensuring the accessibility of digital public services. It describes the situation as of 19 October 2026. The text analysed is the version adopted by the Senate, the upper chamber of the Romanian Parliament, on 1 April 2026 (official page of the bill). Here you will find what I noticed about legal coherence, enforceability, funding and drafting, what the bill does well, proposed amendments and open questions.

Articles are numbered as in the Senate version. V1 means the initial version of the bill. This analysis is not legal advice.

1. In brief

The bill starts from a real problem: digital public services look and work differently from one institution to another. In 2025, monitoring by the Romanian Authority for Digitalisation (ADR), the government body responsible for digitalising public administration, found that only a quarter of the websites checked were accessible (What already exists in Romania, §6). The solution has a clear logic: a common, mandatory standard, the Single Digital Design System (Sistemul Unic de Design Digital, SUDD), also enforced through public procurement.

I noticed a few things about how it would work in practice:

• obligations and fines depend on SUDD, which does not exist yet, and the law sets no deadline for building it;
• the content of the standard is left to a Government Decision (HG), a secondary act adopted by the Government, and to ADR's technical documents;
• in the Senate version, a user's report no longer comes with an obligation to reply;
• each institution pays for its own compliance, with no financial impact statement;
• the Senate added transparency, but set a single fixed date for compliance.

If the bill were adopted as it stands, institutions could be fined before the standard is published.

What I looked at

2. Defining the problem: a real problem, not measured

The problem exists, but the file does not measure it. ADR already collects data on the accessibility of public websites, under Government Emergency Ordinance (OUG) no. 112/2018. The Fiscal Council, the independent body that assesses the budgetary impact of laws, did not give an opinion, because the mandatory financial documents were missing (letter no. 09/03.03.2026). Without a baseline, the evaluation at 36 months (art. 11(4)) would have nothing to compare „costuri reale, economii realizate” (“actual costs, savings achieved”) against.

3. Legal architecture: what SUDD is

3.1 The legal nature of SUDD is not defined

Art. 2(f) defines SUDD as a „mecanism național de standardizare” (“national standardisation mechanism”). The actual requirements are neither in the law nor in the HG. They are in technical documents published by ADR (art. 6(2)(a)) and approved by the National Council for Digital Transformation (CNTD) (art. 7). The law does not say through which act they are adopted. Even so, failing to meet them is a minor offence (contravenție) (art. 4, art. 10). Government Ordinance (OG) no. 2/2001, the general law on minor offences, requires an offence to be clearly established by a legal act. The law also does not say which version a service must comply with, or how long an institution has to adapt to a new version.

3.2 Scope

The law applies to „tuturor organismelor din sectorul public” (“all public sector bodies”) (art. 1(2)), a notion taken from Public Procurement Law no. 98/2016. That means more than 3,000 administrative-territorial units (the local government units), plus schools, hospitals, universities and their associations, with any website, application, terminal or chatbot. However, art. 1(3) applies the law to local authorities only „în condițiile și potrivit calendarului” (“under the conditions and according to the timetable”) set by the HG. “Public service” is not defined.

3.3 The notions that trigger the obligations are defined only in general terms, or not at all

Major modernisation (art. 2(h)), the main trigger, has only a general definition; the criteria are left to the implementing rules. The National Authority for Management and Regulation in Communications (ANCOM), Romania's communications regulator, pointed out the same thing.

Not defined:

• essential malfunctions (art. 5(1));
• sensitive data and major technical constraints, grounds for an exemption (art. 4(5));
• the seven principles (art. 3).

In art. 3(g), „după caz” (“as appropriate”) makes the principle of open standards optional.

4. Enforceability: the order of the steps

4.1 Institutions have deadlines; ADR does not

The obligations do not start only once SUDD is published. A delay at ADR could make institutions liable to fines.

4.2 The fixed date of 1 January 2028

V1 provided for 24 months from entry into force. ANCOM proposed that the period should run from the adoption of the implementing rules. The Senate chose a fixed date. If the Chamber of Deputies adopted the bill in early 2027, the HG would be due around the summer of 2027, and SUDD would follow, with no deadline. That would leave a few months, possibly none, for rebuilding services (my own calculation, based on assumptions). A procurement procedure usually takes longer.

4.3 Projects already under contract are not covered

There are no transitional provisions for procurements already launched, contracts already signed or projects being implemented, including those funded by the EU. Art. 8 covers only „documentațiile de atribuire” (“tender documents”). Applying art. 4(3) and (4) would require contract amendments and extra costs.

4.4 The exemption regime

Only ADR grants exemptions, for at most 12 months, with no extension (art. 4(5)). National security systems receive a temporary exemption, not an exclusion. Lack of funding is not a ground. On the other hand, the existing grounds are vague, with no criteria, no deadline for a decision and no specific route of appeal.

4.5 The HG carries the whole law

Art. 11(3) leaves nine essential elements to the HG: the structure of SUDD, checking before launch, the local timetable, feedback, procurement clauses, bringing existing services into line, technical requirements, exceptions and local support. The law does not say what happens if the HG is not adopted.

4.6 No one is designated to check compliance

Art. 11(3)(b) requires „procedura de verificare a conformității înainte de punerea la dispoziția utilizatorilor” (“the procedure for checking compliance before making (the service) available to users”), without saying who carries it out or with what resources. The requirement could become a formality, or a bottleneck at ADR.

5. Users' rights: what changed in the Senate

The report of the Senate committees cites making the deadline more flexible (ANCOM) and keeping these reports separate from petitions under OG no. 27/2002 (Ministry of Internal Affairs, MAI). Both concerns are legitimate. However, the adopted text leaves fixing to the institution's judgement, based on principles that are not defined. Without a reply, users do not find out whether their report has been read. The right in art. 5(1) remains declaratory, with a greater effect on people with disabilities.

6. Governance: ADR's roles and the CNTD's approval

6.1 ADR builds, regulates, decides and sanctions

ADR builds SUDD and sets its versions (art. 6(2)(a), (b), (g)), supports institutions (points (c), (h), (i)), grants exemptions (art. 4(5)), monitors (art. 6(2)(e), (f)) and imposes fines (art. 10(2)). The law provides no staff or budget for these roles.

6.2 ADR could fine other public institutions

Art. 10 allows ADR, a specialised body of the central administration, to fine ministries, independent authorities and local authorities. The Legislative Council, the advisory body that reviews draft legislation, observed that local councils do not have legal personality and cannot be held liable for minor offences.

6.3 The CNTD's approval (art. 7)

Art. 7 provides that „Consiliul Național de Transformare Digitală avizează documentele și actele care sunt emise de ADR” (“the National Council of Digital Transformation approves the documents and acts issued by ADR”) for the duties in art. 6(2). I checked the consolidated version of HG no. 89/2020, art. 17:

• the CNTD is an „organ consultativ al ADR, fără personalitate juridică” (“advisory body of ADR, without legal personality”) (para. (2));
• its rules of procedure and its members are approved by the president of ADR (paras. (4) and (6)), and members also come from the private sector;
• „Deciziile CNTD au caracter consultativ și rol de recomandare, nefiind obligatorii pentru ADR” (“CNTD decisions are advisory and serve as recommendations, and are not binding on ADR”) (para. (7), amended by HG no. 1.606/2022).

The bill would turn an advisory body into one that gives approval, with members chosen by the institution it approves. It also names it differently: „de Transformare Digitală” (“of Digital Transformation”), compared with „pentru transformare digitală” (“for digital transformation”) in the HG. ADR has announced that CNTD members include private-sector organisations. Private-sector members would therefore take part in approving requirements that then apply in procurement (art. 8). Approval for every update would slow down a system that is updated often. No link in the proposal–approval–sanction chain is independent of ADR.

6.4 Users and civil society have no defined role

Users appear only as senders of feedback (art. 5) and authors of „contribuții controlate” (“controlled contributions”) (art. 6(2)(g)). Organisations of people with disabilities have no role in governance or testing.

7. Sanctions

A stronger lever would be making funding conditional: no approval and no payment for a non-compliant project.

8. Funding

1. There is no financial impact statement. The Fiscal Council formally requested one (Law no. 69/2010, art. 15(1)). The file shows no reply, and the Senate voted without it.
2. Art. 9(1) calls the expenditure „investiții prioritare în transformare digitală” (“priority investments in digital transformation”), with no budgetary effect.
3. Art. 9(2) requires each body to pay „în limita creditelor bugetare aprobate” (“within the limits of the approved budget appropriations”). A body without a budget cannot comply, but can be fined. For local authorities this is an unfunded obligation, hard to reconcile with Framework Law no. 195/2006 on decentralisation.
4. Art. 6(2)(h) requires ADR to provide „mecanisme concrete de sprijin financiar” (“concrete financial support mechanisms”), without a legal instrument for them.
5. The Constitution (art. 138(5)) requires a source of funding for any expenditure. The formula „în limita creditelor bugetare aprobate” (“within the limits of the approved budget appropriations”) is often accepted, but a law with new expenditure for every body, and no financial impact statement, could be challenged at the Constitutional Court (CCR) after the vote in the Chamber of Deputies.

9. Drafting problems

10. The procedure

1. The Senate adopted the bill 16 days after it was registered as L167/2026 (57 days after it was submitted). The final vote was 96–1.
2. The amendments cite „sugestii” (“suggestions”) from the Ministry of Economy, Digitalisation, Entrepreneurship and Tourism (MEDAT), the MAI, the Ministry of Justice (MJ) and the Association of Municipalities of Romania (AMR). These documents are not in the public files.
3. The Government's point of view, requested on 9 February 2026, does not appear in the file.
4. The fiscal question has remained unanswered (§8).
5. The report of the Chamber of Deputies, the lower chamber of Parliament, was due on 5 May 2026 and has not appeared. The government programme proposed on 15 October 2026 announces a law on „guvernanței digitale integrate” (“integrated digital governance”). Details in The bill's legislative journey.

11. What the bill does well

The bill has important strengths that would be worth keeping in any final version:

• It treats design as infrastructure. Shared components, flows, templates and content guidelines become a legal subject, not a matter of taste. This is the right approach for a problem that recurs in every institution.
• It also covers existing services, not just new ones.
• It uses public procurement as a lever (art. 8). The direction is good, even if checks are still missing.
• It requires compliance with SUDD „de la inițierea proiectului” (“from the start of the project”) (art. 4(3)), meaning the requirements apply from the design phase of a service.
• The Senate added solid transparency:
• an annual public report, with compliance percentages by county (art. 6(2)(f));
• published exemptions;
• SUDD as a fully open-source resource („open-source integrală”), open to contributions (art. 6(2)(g));
• an independent evaluation, with actual costs and savings achieved, after 36 months (art. 11(4)).
• The principles are well chosen (art. 3), especially plain language and accessibility.
• It includes self-service terminals and chatbots.
• It is technology-neutral. It does not impose a supplier or a technology.

12. Proposed amendments

Priority, before the vote in the Chamber of Deputies

1. Restoring the wording „cu titlu gratuit” (“free of charge”) and an explicit open licence.
2. Deadlines that run from the publication of SUDD, with a deadline for the first version, instead of the date of 1 January 2028.
3. A user right that can actually be exercised: without „dacă consideră” (“if they consider”), with a deadline for replying and referral to ADR, separate from petitions.
4. SUDD requirements adopted through an act published in the Official Gazette (Monitorul Oficial), with a fixed transition period for each version.
5. The financial impact statement and a reply to the Fiscal Council.

Necessary

6. Objective criteria for “major modernisation” and definitions of the principles in art. 3.
7. Making funding conditional instead of fines; art. 8 checked through the procurement and funding authorities.
8. The CNTD replaced by public consultation and an advisory council including organisations of people with disabilities and local government; approval only for major versions.
9. Checking and sanctioning kept separate from building the standard, with a route of appeal.
10. Transitional provisions for ongoing contracts.
11. Excluding national security systems, exemptions that can be extended, and a ground for lack of local funding.

Optional

12. A real source of funding for local authorities.
13. The training programme (art. 6(2)(i)) either completed or removed.
14. An explicit role for organisations of people with disabilities.
15. Staff interfaces regulated explicitly.
16. Publishing the contributions from MEDAT, the MAI, the MJ and the AMR.

13. Open questions

1. How many services and websites fall under the law, and how many are local?
2. How many people and how much money would ADR need? When would the first version of SUDD appear?
3. Who checks compliance before launch?
4. Through which act are the requirements published, and how does anyone know which version applies?
5. How can the CNTD's advisory role under HG no. 89/2020 be reconciled with the approval in art. 7?
6. How can a double fine under OUG no. 112/2018 and art. 10 be avoided?
7. Why did the Senate remove the 30-day deadline instead of adjusting it?
8. How does a town hall with no IT budget comply by 1 January 2028?
9. Will the financial impact statement requested by the Fiscal Council be submitted?
10. How does the bill relate to the law on integrated digital governance announced in the government programme of 15 October 2026?
11. Will the Chamber of Deputies correct the „cu titlu” error?

Sources

• Chamber of Deputies: page for bill PL-x 300/2026, with the text adopted by the Senate and the opinions
• Romanian Senate: page for bill L167/2026
• Romanian Senate: final plenary vote, 1 April 2026
• Agerpres: the government programme and the law on integrated digital governance, 16 October 2026

← All research documents