Introduction

ASP.NET Web Forms GridView does not always emit a semantic table header section by default, which is why developers often end up with header rows rendered only as ordinary tr elements. If you want the control to output a real thead, the usual fix is to mark the header as accessible and assign the header row to TableHeader after data binding.

Why GridView Does Not Always Render thead

GridView is a server control, so the HTML it emits depends on its internal rendering rules. Even if the control visually shows a header row, that does not guarantee it will produce a thead section in the final markup.

That matters for a few reasons:

• screen readers understand table structure better
• CSS targeting of headers is cleaner
• client-side table plugins often expect semantic sections
• the markup is more correct and maintainable

So the problem is not "how do I style the header." The problem is "how do I make GridView render semantic header markup."

The Standard Fix in Code-Behind

The most common solution is:

1. make sure the control has a header
2. enable accessible header rendering
3. set the header row section to TableHeader

This is often done after the grid has been bound:

1<asp:GridView ID="OrdersGrid"
2    runat="server"
3    AutoGenerateColumns="False"
4    OnPreRender="OrdersGrid_PreRender">
5    <Columns>
6        <asp:BoundField DataField="Id" HeaderText="Order ID" />
7        <asp:BoundField DataField="Customer" HeaderText="Customer" />
8        <asp:BoundField DataField="Total" HeaderText="Total" />
9    </Columns>
10</asp:GridView>

Code-behind:

1using System;
2using System.Web.UI.WebControls;
3
4public partial class Orders : System.Web.UI.Page
5{
6    protected void Page_Load(object sender, EventArgs e)
7    {
8        if (!IsPostBack)
9        {
10            OrdersGrid.DataSource = new[]
11            {
12                new { Id = 1, Customer = "Ana", Total = 125.50m },
13                new { Id = 2, Customer = "Sam", Total = 89.00m }
14            };
15            OrdersGrid.DataBind();
16        }
17    }
18
19    protected void OrdersGrid_PreRender(object sender, EventArgs e)
20    {
21        if (OrdersGrid.HeaderRow != null)
22        {
23            OrdersGrid.UseAccessibleHeader = true;
24            OrdersGrid.HeaderRow.TableSection = TableRowSection.TableHeader;
25        }
26    }
27}

The PreRender event is a good place for this because the rows already exist by then.

Why UseAccessibleHeader Matters

Setting HeaderRow.TableSection = TableRowSection.TableHeader is the key step, but UseAccessibleHeader = true is also important because it instructs the control to render header cells with th semantics instead of ordinary data cells.

Together, these settings produce the kind of output most developers expect:

• the header row is placed inside thead
• header cells render as th
• body rows stay inside tbody

If you only set one of these properties, the output may still not be as semantic or predictable as you want.

Handle Empty Data Carefully

One reason the fix sometimes appears not to work is that the grid has no header row at all when there is no data. If HeaderRow is null, there is nothing to assign to TableHeader.

For grids that must show headers even when empty, configure the control accordingly and verify the final rendered HTML in the browser. The presence or absence of a data source affects whether HeaderRow exists during PreRender.

Another practical tip is to inspect the actual page source rather than relying on what the server control "should" be doing. Web Forms can be surprising if you only reason from markup and do not check the emitted HTML.

Common Pitfalls

The biggest mistake is setting TableSection too early, such as before the grid is bound. At that point the header row may not exist yet.

Another issue is forgetting UseAccessibleHeader = true. Without it, the control may still render a row, but not with the semantic header cell behavior you expect.

Developers also sometimes confuse design-time markup with runtime output. The important thing is what the browser receives, not what the .aspx file suggests.

Finally, when the grid is empty, HeaderRow can be null. If your logic does not guard against that case, the code either fails or silently does nothing.

Summary

• To get GridView to render a real thead, set UseAccessibleHeader = true and assign HeaderRow.TableSection = TableRowSection.TableHeader.
• Do this after data binding, commonly in the PreRender event.
• Check that HeaderRow is not null before modifying it.
• Inspect the final HTML output to confirm the browser receives semantic table markup.
• If the grid is empty, you may need additional configuration to keep a header row available.