HTML

Figma Sites generates only `<div>` elements without semantic HTML, making it impossible to create accessible websites that comply with WCAG standards. This poses litigation risk for businesses and prevents proper semantic structure required for screen readers and keyboard navigation.

Developers frequently fail to properly connect labels to form elements by using the name attribute instead of id. Labels must be connected to elements via ID (which is unique per element), not name (which clusters form elements together), leading to accessibility failures and poor UX.

Developers pile HTML into pages without proper structure, then struggle when CSS cannot fix poor document architecture. Effective CSS layout depends on developers first understanding how to structure HTML semantically and logically.

The new accordion pattern using grouped <details> elements has unresolved accessibility limitations. Using <details> elements doesn't preserve proper semantic heading hierarchy (e.g., in FAQ sections where headers would normally be <h2>), and the one-open-at-a-time behavior can cause unintended closures and horizontal scroll issues.

Tauri forces backend developers to learn HTML, CSS, and JavaScript, and vice versa. There are no native UI components—the entire interface relies on web technologies. This creates a barrier for teams specialized in desktop or backend development and requires hiring full-stack developers or extensive training.

HTML features and best practices evolve regularly, but developers struggle to keep up with the pace of new features and understand how to use them correctly. The learning curve is exacerbated by slower documentation and lower visibility compared to CSS and JavaScript.

While responsive design is necessary to accommodate different screen sizes, its successful implementation remains challenging. Developers must balance complexity and functionality across diverse device types and screen resolutions.

Developers deprioritize HTML quality because browsers are forgiving and fix broken HTML automatically. This leads to lazy development practices where incorrect HTML is tolerated if it doesn't break the build, despite the long-term maintenance and performance costs.

Tailwind's utility-class approach promotes overuse of generic `<div>` and `<span>` tags instead of semantic HTML elements, leading to less accessible and maintainable markup that doesn't leverage modern custom elements.

Creating accessible and properly structured HTML tables is cited as one of the most complex HTML structures. Developers struggle with both creating data tables and making them accessible.

Developers frequently make preventable mistakes including missing character encoding declarations, improperly formatted tags (missing closing tags, incorrect self-closing tag usage), and incorrect attribute formatting. These cause rendering issues and structural problems.