With the Framer API, it appears that there isn't a way to render something like <header>, <figure>, or any other semantic HTML elements with <Frame> — this is likely not limited to just <Frame>. This means that using the Framer API on the web is very limited; to maintain accessibility on a website you would not be able to use <Frame> in specific parts of the code.
Here is an example that is taken straight from the "Examples" section of the documentation:
What I'm proposing is that — to allow semantic HTML elements to be used, a necessity for accessibility on the web — an as prop would be added for any component that can currently only render a <div>; the as prop has become quite commonplace in the React community.
With the Framer API, it appears that there isn't a way to render something like
<header>
,<figure>
, or any other semantic HTML elements with<Frame>
— this is likely not limited to just<Frame>
. This means that using the Framer API on the web is very limited; to maintain accessibility on a website you would not be able to use<Frame>
in specific parts of the code.Here is an example that is taken straight from the "Examples" section of the documentation:
The above code would render a
<div>
in HTML like so:Solution
What I'm proposing is that — to allow semantic HTML elements to be used, a necessity for accessibility on the web — an
as
prop would be added for any component that can currently only render a<div>
; theas
prop has become quite commonplace in the React community.